Monitoring
GitLab.com · degraded service
GitLab.com CI/CD Incident
Started today 11:33 UTC; still ongoing when ChangeIntel last read it, 1 min ago.
What it affected
As the provider names itWhat the provider posted
Newest first- today 12:28 UTCMonitoringWe've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.
- today 11:33 UTCInvestigatingWe’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
- today 11:33 UTCInvestigatingWe’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
Earlier incidents in the 14 days before
- 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
- GitLab.com: Increase of HTTP 50X errors on GitLab.comService incident · 13 Oct
What changed
First observed 16 Oct 2026- 16 Oct 2026 StageInvestigating → Monitoring
- 16 Oct 2026 SummaryWe’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow. → We've applied a temporary mitigation to address CI/CD failures and UI slowness affecting a limited number of GitLab.com customers. We're monitoring recovery while working on a longer-term solution.
- 16 Oct 2026 SummaryWe’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow. → We’re investigating an issue affecting CI/CD on GitLab.com for a limited number of customers. Pipelines may fail with the following error, and the UI may be slow: “CI configuration fetch from Gitaly timed out. This may indicate Gitaly service slowness or an outage.” More updates to follow.
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.