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.
Daily CI/CD & runners uptime measured by OutageDeck's own independent checks, rolled up per UTC day. Days without monitoring data stay empty rather than counting as uptime.
99.27%free of major outages · last 90 days
Last 30 days: 98.89%. 7h 48m of major outage and 50m of partial or regional impact across 46 monitored days.
Tracking since Jul 23, 2026
Only the incidents GitLab reported against this specific service, so you can tell a targeted problem from a platform-wide one.
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.
Performance remains stable and prevention steps are being implemented. Find more information here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22807
The elevated 403 errors affecting GitLab.com have been resolved and error rates have returned to normal levels. More details in: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22762
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.