Circle CI Outage History

Customers using Bitbucket as their VCS provider or as their login provider experienced errors when interacting with Bitbucket repositories and authenticating to CircleCI. This was caused by an incident with Atlassian Bitbucket's OAuth service, which has now been resolved and all affected functionality has returned to normal.

This incident has been resolved.

This incident has been resolved.

Between 13:29 UTC and 18:20 UTC on June 9, 2026, some customers experienced 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs running were not impacted during this window. The issue has been resolved and all affected functionality has returned to normal. We thank you for your patience while our team worked on implementing a fix.

This issue has been resolved and macOS jobs across all resource classes are starting normally again. Customers whose jobs failed to start during this window may rerun them. We thank you for your patience while our team worked on implementing a fix.

This incident has been resolved.

All Mac jobs are running successfully. Our infrastructure provider has confirmed that the DDoS attack has been mitigated and that services have been restored. Thank you for your patience during this incident.

The Usage API incident has been resolved.

Customers running jobs that pulled dependencies from Maven Central experienced elevated 429 (rate limit) errors. We have worked with Sonatype to allow list CircleCI's dedicated IP ranges. Customers using our IP ranges feature should no longer see Maven Central rate limits affect their jobs while we continue work to fully address the issue for all customers. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.

This incident is resolved. Thank you for your patience, and we apologize for any inconvenience.

This incident has been resolved.

This incident has been resolved.

This issue has been resolved. All data is up to date through yesterday.

Customers running macOS jobs on m4pro.medium and m4pro.large with the xcode:26.4.0 image experienced job rejections with the error: "Job was rejected because resource class , image xcode:26.4.0 is not a valid resource class". The issue has been resolved and affected jobs should now run normally. Customers whose jobs failed may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.

The Usage API issue has been resolved. All data is now current. Appreciate your patience.

The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.

The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.

It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.

On March 18, 2026, customers using workflows configured with serial groups or terminal job dependencies experienced two brief periods of disruption due to a code change. Between approximately 12:08 and 12:35 UTC, affected pipelines encountered errors when creating workflows. For pipelines created in a second window from approximately 14:23 to 14:35 UTC, GitHub status updates were not delivered for some completed jobs. Long-running workflows triggered during this window may encounter these errors after the resolution time. The underlying change was reverted in both cases. All systems have been operating normally since 14:35 UTC.

Our engineering team has identified the root cause and has fixes prepared. Due to the nature of the data refresh process, the fix will require a deployment followed by a full refresh cycle before data is fully up to date. We expect that the data should be available within 24-36 hours. The last-24-hours reporting window continues to work normally, and all pipeline pages and job runs remain unaffected.

The issue affecting the orb list on the Organization Settings page has been resolved. Our engineers have deployed a fix and users should now be able to view their orb list as expected. Orb usage in pipelines and builds was not impacted during this incident. If you continue to experience issues, please contact CircleCI support. Thank you for your patience while we worked on resolving this issue.

Looks like everything is good. Thank you for your patience.

GitHub have acknowledged and resolved an incident affecting their platform. https://www.githubstatus.com/incidents/vd3xqfq36rgm Users should no longer experience intermittent checkout failures.