The issue causing CI/CD failures and UI slowness for a limited number of GitLab.com customers has been resolved. Thank you for your patience.
GitLab CI/CD & runners status
CI/CD coverage tracks GitLab pipelines and the hosted runner fleets on Linux, Windows, and macOS.
A service of GitLab. Read it at the source: service documentation.
The same reading is on the service JSON API, no account needed.
CI/CD & runners uptime history
Daily CI/CD & runners status as reported by the official source that publishes it, read about every 10 minutes and rolled up per UTC day. Days without a reading stay empty rather than counting as uptime.
99.58%free of major outages · last 90 days
Observed 99.6% of the last 90 days; 7h 12m unobserved.
Last 30 days: 99.84%. 8h 53m of major outage and 15h 28m of partial or regional impact across 90 days on record.
Tracking since Jul 24, 2026
- Operational
- Degraded
- Partial outage
- Major outage
- Maintenance
- No data
Incidents impacting CI/CD & runners
Incidents from GitLab's official feed that OutageDeck matched to this service.
We have taken steps to mitigate the delays on CI/CD jobs on GitLab.com and services have returned to normal. More details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23234
The source of the issue has been identified and we have taken steps to remediate and resolve the issue. GitLab.com is stable now. More details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/23192
Job start times for CI/CD jobs on GitLab.com small Linux x86-64 hosted runners have returned to normal, and the backlog of pending jobs has been processed. The issue with the provider persists, but we are not seeing any impact on our systems. More details: gitlab.com/gitlab-com/g
The incident affecting CI/CD jobs on GitLab.com instance runners has been resolved. Following a period of monitoring, everything has remained stable. Details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23117
Jobs on saas-linux-small-amd64 hosted runners have been processing as expected, and this incident is now resolved. Details at: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23077
The incident affecting GitLab.com CI/CD jobs using instance runners is now resolved. Some jobs were delayed or remained pending while a manually initiated pg_repack database maintenance operation caused contention on the CI database, affecting runner communication and job pickup.
The error rate remains within normal thresholds and the issue is now resolved. Further details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
The queue of pending jobs on the affected runners has returned to normal and has stayed at that level. This incident is now resolved. Please open a ticket with support if you are still seeing job delays. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702
We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
Put GitLab CI/CD & runners status in your README
A live SVG badge for this one service, not the whole platform. It reads GitLab's official feed, needs no account or API key, and links back to this page.
Markdown
[](https://outagedeck.com/services/gitlab-ci)HTML
<a href="https://outagedeck.com/services/gitlab-ci"><img src="https://outagedeck.com/api/v1/badges/services/gitlab-ci" alt="GitLab CI/CD & runners status" /></a>Want the whole vendor instead? The GitLab page carries its own badge, and the embed builder builds a status wall for several vendors at once.