GitLab: SLA evidence report
GitLab: SLA evidence report
We hold no probe record for GitLab: we read its status page, so the only incident record here is what GitLab declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents GitLab declared
- 15
- On its own status page, in this window.
- Window
- 2026-10-08 to 2026-11-07
- UTC, 30 days.
Oct 8, 2026, 3:59 PM UTC to Oct 8, 2026, 6:33 PM UTC
Delayed job completion, impact minor
This incident started before the report window shown above.
Oct 10, 2026, 4:49 AM UTC to Oct 12, 2026, 10:15 AM UTC
Errors and slow performance on merge requests in the specific groups., impact minor
Oct 12, 2026, 11:30 AM UTC to Oct 14, 2026, 1:16 AM UTC
GitLab Duo Workflow Issues, impact minor
Oct 13, 2026, 7:10 AM UTC to Oct 14, 2026, 11:40 PM UTC
Increase of HTTP 50X errors on GitLab.com, impact minor
Oct 13, 2026, 2:27 PM UTC to Oct 13, 2026, 8:59 PM UTC
Job delays on saas-linux-small-amd64 hosted runners, impact minor
Oct 14, 2026, 2:33 PM UTC to Oct 14, 2026, 6:30 PM UTC
GitLab.com CI/CD pipelines delayed or not starting, impact minor
Oct 15, 2026, 4:43 AM UTC to Oct 15, 2026, 9:02 AM UTC
Error loading GitLab.com and customers.gitlab.com, impact minor
Oct 15, 2026, 4:19 PM UTC to Oct 15, 2026, 7:50 PM UTC
CI/CD Job Delays on GitLab.com, impact minor
Oct 16, 2026, 11:33 AM UTC to Oct 16, 2026, 1:21 PM UTC
GitLab.com CI/CD Incident, impact minor
Oct 16, 2026, 4:10 PM UTC to Oct 16, 2026, 5:24 PM UTC
503s on GitLab.com, impact minor
Oct 20, 2026, 7:08 AM UTC to Oct 20, 2026, 9:55 AM UTC
Intermittent 500 on GitLab.com, impact minor
Oct 20, 2026, 9:56 PM UTC to Oct 21, 2026, 1:21 AM UTC
404s on customers.gitlab.com, impact minor
Oct 23, 2026, 4:32 PM UTC to Oct 23, 2026, 5:04 PM UTC
General slowness on Gitlab.com, impact minor
Nov 3, 2026, 5:06 AM UTC to Nov 3, 2026, 9:51 AM UTC
Elevated CI/CD latency on GitLab.com, impact minor
Nov 3, 2026, 5:20 PM UTC to Nov 3, 2026, 6:51 PM UTC
Issues Running Pipelines, impact minor
Methodology
These incidents come from GitLab's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit GitLab owes, if any, is decided under its own SLA.