Circle CI Outage History

Circle CI experienced a major incident where some pipelines were being lost, affecting the Pipelines & Workflows components. The engineering team rolled back the affected service, which successfully restored normal pipeline flow. The incident was resolved after 35 minutes of downtime.

GitHub experienced a major incident with degraded pull request availability that lasted 3.6 hours. CircleCI builds for newly created pull requests and push events continued to function normally during the GitHub outage. The incident was resolved after monitoring confirmed no further issues.

Circle CI experienced delays affecting jobs using Xcode 14.3.1 on m4pro.large instances, impacting macOS job execution. The issue was identified and resolved with a fix implementation within 19 minutes of the initial investigation.

Circle CI's Usage API experienced delayed data for April 30th, while all prior data remained available. The issue was classified as minor and was resolved after 4 hours, with all data brought up to date.

Circle CI experienced build failures affecting macOS jobs using Xcode 26.4.0 on m4pro.medium and m4pro.large resource classes, with jobs being rejected due to an invalid resource class configuration error. The incident lasted 1.2 hours and was resolved by implementing a fix to restore normal job execution. Customers were advised to rerun any jobs that failed during the outage period.

Circle CI's Usage API experienced data delays for 3 hours on April 18th, 2026. The issue was identified and a fix was implemented by the engineering team. The problem was resolved and all API data returned to current status.

Circle CI experienced delays in workflow and job data delivery through their Usage API, with some data from the last 24 hours not being fully reflected due to a backlog of events. The Insights UI remained unaffected during the incident. The issue was resolved after 7.3 hours, though a 4-hour period of RAM and CPU utilization data from April 7th was permanently lost and will not be backfilled.

CircleCI experienced a 40-minute degradation affecting UI elements, specifically approval jobs and SSH key navigation functionality. The issue was limited to the interface only, with builds continuing to operate normally throughout the incident. The problem was resolved after implementing a fix and monitoring the results.

Circle CI's Usage API experienced incomplete data for April 1st, with multiple columns showing null values while data from other dates remained unaffected. The issue was identified and a fix was implemented, with the corrected data becoming available on April 3rd after a 7-hour resolution period.

Circle CI experienced a major service incident where some pipelines failed to trigger due to high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API endpoint. The issue affected manually-triggered pipelines, OAuth hooks, and scheduled pipelines for 33 minutes. The incident was resolved when GitHub's API endpoint became stable and responsive again.