Search

Changes / GitLab / Investigating GitLab.com Access Issues

GitLab: Major incident: Investigating GitLab.com Access Issues

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: outage (model (Jev), 51%)Changed Detected Source: status.gitlab.com (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: Investigating GitLab.com Access Issues
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-08-27 07:12 UTC
AddedResolved time#5
Before: not present
After: 2026-08-27 09:35 UTC
AddedAffected components#6
Before: not present
After: API, Website
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating reports of connectivity issues affecting some users accessing GitLab.com.
AddedUpdatemonitoring#8
Before: not present
After: We have identified a temporary filtering event by an upstream provider that affected some traffic to GitLab.com. The event has ended, and we are working with our service provider to investigate the cause and prevent recurrence. We are monitoring the situation to ensure that services have returned to normal.
AddedUpdateresolved#9
Before: not present
After: Our upstream provider mitigated a genuine distributed HTTP DDoS attack against gitlab.com, but incorrectly blocked a small amount of legitimate traffic. This has now been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Investigating GitLab.com Access Issues (this change)Major incident

All GitLab changes → · GitLab profile · Markdown · JSON