WhatBrokeToday
GTA 6FAQ

CircleCI vs GitHub: reliability

In the last 60 days, CircleCI had 14 incidents (median fix 1 min) and GitHub had 53 incidents (median fix 1 min). CircleCI broke less often.

Side by side, last 60 days

CircleCI and GitHub reliability over the last 60 days
MeasureCircleCIGitHub
Incidents (60 days)1453
Critical or high220
Median time to fix1 min1 min
Longest incident1 min13 days
Never on its status page018
Status page delay (median)1 min1 min
30-day hazard rating2.7 / 1010.0 / 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

GitHub's worst incidents

GitHub's worst incidents in the last 60 days
DateIncidentSeverityTime to fixStatus page
GitHub: Incident with Webhookscritical1 hfirst
GitHub: Incident with Git Operations and Pull Requestscritical2 hfirst
GitHub: Incident with Actions and Checks API

Cause: An issue with an upstream model provider caused degraded availability for specific models in Copilot products and IDE surfaces.

critical3 daysfirst
GitHub: Disruption with GitHub servicescritical28 min+28 min
GitHub: Degraded availability for GitHub Actions, GitHub Pages and Webhookscritical3 days+3 days
Full GitHub outage history