Recorded 16 Oct 2026 at 17:25 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.
503s on GitLab.com
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
What it said
- Observed state
- Ended
- Stage
- Monitoring
- Started
- 16 Oct 2026 16:10 UTC
- Services
- Website, API, Git Operations, Package Registry, Container Registry, GitLab Pages, CI/CD, CI/CD - Hosted runners on Linux, CI/CD - Hosted runners on Windows, CI/CD - Hosted runners on macOS, CI/CD - Hosted runners for GitLab community contributions, CI/CD - Self-managed runners, SAML SSO - GitLab SaaS, Background Processing, GitLab Customers Portal, Support Services, packages.gitlab.com, version.gitlab.com, forum.gitlab.com, docs.gitlab.com, Canary, GitLab Duo, GitLab agent server for Kubernetes
Recorded links
What changed
First observed 16 Oct 2026- 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.