Monitoring
GitLab.com · outage
503s on GitLab.com
Started today 16:10 UTC, left the provider's feed by today 17:25 UTC: at least 1 h 10 min.
1 h 10 min+
At least, from when ChangeIntel read it
5Updates posted
What it affected
As the provider names itWhat the provider posted
Newest first- today 17:05 UTCMonitoringWe have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- today 16:52 UTCIdentifiedMost services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- today 16:40 UTCIdentifiedWe have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- today 16:25 UTCInvestigatingWe are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- today 16:10 UTCInvestigatingWe are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details.
Around it
From the sources ChangeIntel reads; a match in time is not a causeEarlier incidents in the 14 days before
- GitLab.com: GitLab.com CI/CD IncidentService incident · 16 Oct
- GitLab.com: CI/CD Job Delays on GitLab.comService incident · 15 Oct
- GitLab.com: Error loading GitLab.com and customers.gitlab.comService incident · 15 Oct
- GitLab.com: GitLab.com CI/CD pipelines delayed or not startingService incident · 14 Oct
- GitLab.com: Job delays on saas-linux-small-amd64 hosted runnersService incident · 13 Oct
What changed
First observed 16 Oct 2026- 16 Oct 2026 Observed stateOngoing → Ended
- 16 Oct 2026 StageIdentified → Monitoring
- 16 Oct 2026 SummaryMost services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 → We have taken steps to resolve the slowness and 503s on GitLab.com and are monitoring the situation. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- 16 Oct 2026 SummaryWe have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 → Most services on GitLab.com have recovered but we are seeing slowness with Duo requests and services and are looking to resolve it. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- 16 Oct 2026 StageInvestigating → Identified
- 16 Oct 2026 SummaryWe are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261 → We have identified the cause of 503s on GitLab.com and are working to remediate the issue. We are still seeing intermittent 503s and site slowness as we work to resolve the issue. More details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
- 16 Oct 2026 SummaryWe are investigating the cause of 503s on GitLab.com and the site moving slowly. We will update once we have additional details. → We are still investigating the cause of 503 on GitLab.com. We are seeing some services return but errors still intermittent. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23261
The most recent 100 field changes are listed. Complete recorded revisions are kept separately.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about GitLab: its changes, known issues and incidents on one timeline.