Outage alerts
CheckedEmail alerts are free for up to 5 providers, and Slack, Teams, Discord, and webhook delivery come with paid plans. Every alert is driven by GitLab's official status feed, checked about every 10 minutes around the clock.
Why it matters
GitLab was free of major outages 99.27% of observed time across 46 monitored days in the last 90 days, including 7h 48m of major outage and 25h 26m of partial or regional impact. The official feed logged 25 incident entries in that window. Those are exactly the changes subscribers hear about first.
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
Alerts can cover the whole platform or just the parts you depend on. Narrowing means you hear about incidents affecting that service, not every GitLab status change.
New incident
A fresh incident appeared on the official feed and started within the last 24 hours. Historical backfills never alert.
Incident update
An open incident moved through its lifecycle (investigating → identified → monitoring …).
Incident resolved
An incident was resolved upstream, or disappeared from the provider's active feed.
Status change
The provider's overall status flipped (e.g., Operational → Partial outage).
Every delivery is claimed exactly once per event, retried once on failure, and recorded, so overlapping check runs can never double-notify you. Alerts are driven by GitLab's official status source: the official GitLab status page remains the authoritative reference.
Everything on this page is also machine-readable, free, and account-less: subscribe to the GitLab RSS feed, poll the JSON API, or embed the live GitLab status badge in a README or dashboard.
FAQ
Short answers to what alert subscribers ask most.
OutageDeck checks GitLab's official status feed about every 10 minutes, around the clock. The first check that sees a new incident or a status change fires your alert immediately, so email, Slack, Teams, Discord, and webhook subscribers typically know within minutes of the official feed changing.
Yes. Every account includes free email alerts for up to 5 providers, no card required. Paid plans add Slack, Teams, Discord, and webhook delivery, more subscriptions, and higher API quotas.
New incidents on the official feed (when they started within the last 24 hours), incident lifecycle changes, resolutions, and provider-level status changes. A subscription can watch just GitLab, and on a paid plan your whole stack or individual GitLab services.
Yes. The GitLab RSS feed, the public JSON API, and the embeddable status badge are free with no sign-up. Alerts exist so changes get pushed to you instead of you re-checking a page.
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.