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's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| CircleCI: Delay in data appearing in UI and API | high | 1 min | first | |
| CircleCI: Delays in pipelines, workflows, UI data, and notifications | high | 1 min | first | |
| CircleCI: Increased wait time for Machine and Remote Docker jobs Cause: Increased usage leading to capacity constraints for Machine and Remote Docker jobs. | medium | 1 min | first | |
| CircleCI: Delays for gen2 dedicated IP range jobs Cause: Limited compute availability from the cloud provider | medium | 1 min | first | |
| CircleCI: Increased Docker gen2 wait times | medium | 1 min | first |
GitHub's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| GitHub: Incident with Webhooks | critical | 1 h | first | |
| GitHub: Incident with Git Operations and Pull Requests | critical | 2 h | first | |
| 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. | critical | 3 days | first | |
| GitHub: Disruption with GitHub services | critical | 28 min | +28 min | |
| GitHub: Degraded availability for GitHub Actions, GitHub Pages and Webhooks | critical | 3 days | +3 days |