WhatBrokeToday
GTA 6FAQ

CircleCI vs GitLab: reliability

In the last 60 days, CircleCI had 14 incidents (median fix 1 min) and GitLab had 14 incidents (median fix 1 min). They broke equally often.

Side by side, last 60 days

CircleCI and GitLab reliability over the last 60 days
MeasureCircleCIGitLab
Incidents (60 days)1414
Critical or high24
Median time to fix1 min1 min
Longest incident1 min1 min
Never on its status page05
Status page delay (median)1 min1 min
30-day hazard rating2.7 / 104.7 / 10

CircleCI's worst incidents

CircleCI's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
CircleCI: Delay in data appearing in UI and APIhigh1 minfirst
CircleCI: Delays in pipelines, workflows, UI data, and notificationshigh1 minfirst
CircleCI: Increased wait time for Machine and Remote Docker jobs

Cause: Increased usage leading to capacity constraints for Machine and Remote Docker jobs.

medium1 minfirst
CircleCI: Delays for gen2 dedicated IP range jobs

Cause: Limited compute availability from the cloud provider

medium1 minfirst
CircleCI: Increased Docker gen2 wait timesmedium1 minfirst
Full CircleCI outage history

GitLab's worst incidents

GitLab's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
GitLab Backup Procedure Fails Due to PostgreSQL Major Version Mismatch

Cause: A difference in major versions between pg_dump (9.2) and the running PostgreSQL database (9.6) caused pg_dump to produce an error and end the backup.

highongoingnot yet
GitLab: Issues Running Pipelineshigh1 minfirst
GitLab Security Incident: Attempted Exploitation of CVE-2026-97229high1 minnever
GitLab Outagehighongoingnot yet
GitLab: CI/CD Job Delays on GitLab.commedium1 minfirst
Full GitLab outage history