There were 19 Circle CI outages since February 3, 2026 totaling 32h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating the cause.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating
This issue has been resolved. All data is up to date through yesterday.
There are build failures for Xcode 26.4.0; we have identified the issue and are currently implementing a fix.
A fix has been implemented and we are monitoring the results.
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.
Usage API data is delayed this morning. Team is investigating.
The Usage API issue has been identified and a fix is being implemented. We expect to the issue be resolved within a few hours.
The Usage API issue has been resolved. All data is now current. Appreciate your patience.
We have identified an issue causing Insights workflow and job data to be delayed when requested through the Usage API. Some data for the last 24 hours may not be fully reflected while we work to process the backlog of events. Insights UI is not impacted by this issue. Thank you for 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.
We are currently investigating an issue in the CircleCI UI impacting approval jobs and SSH key navigation. This is an interface-only issue and builds continue to flow as usual.
A fix has been implemented and we are monitoring the results. Thank you for your patience.
This incident has been resolved.
**What happened** All modals and dialogs across the CircleCI application became invisible. They were being rendered correctly in the background, but were not visible to users. This affected approval jobs, SSH key management, and other settings pages across the app. **Root cause** The issue was introduced by an upgrade to our internal design system library. The new version added animation support to modal components using a library called Framer Motion. These animations are designed to fade modals in from invisible \(`opacity: 0`\) to visible \(`opacity: 1`\) when opened. However, the animation logic reads open/close state from a specific React context that is only available when modals are opened via a particular component \(`DialogTrigger`\). Our application manages modal state differently, passing open/close state directly via props, so that context was never populated. As a result, every modal in the app was permanently stuck in the "hidden" animation state and never transitioned to visible. **Resolution** We reverted the design system upgrade to restore the previous working version, which resolved the issue immediately. We are now working on a follow-up fix that will upgrade Framer Motion properly, by ensuring all modal components receive the required context. **Impact** The issue affected all modal dialogs across project settings, org settings, user settings, plans & payments, and other areas of the app for the duration of the incident. No data was lost or corrupted. The underlying functionality was intact, just inaccessible via the UI.
We are currently investigating this issue.
The Usage API issue has been identified and the fix is being implemented.
The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.
Some pipelines may not trigger due to a high rate of API failures on one of GitHub's API endpoints. This includes some manually-triggered pipelines, some OAuth hooks and some scheduled pipelines.
We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.
GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.
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.
We are investigating an issue where the Insights API and dashboard are returning outdated metrics for reporting windows longer than 24 hours (last 7 days, last 30 days, last 60 days, last 90 days). The last-24-hours window is unaffected and returning current data. This issue is limited to the display of aggregated metrics on Insights Page only. All pipeline pages, job runs, and builds remain fully operational and are not impacted. We will provide updates as our investigation progresses.
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.
We are investigating an issue where users are unable to view their organization's orb list on the Organization Settings page. The page may appear blank or fail to load the expected list of public and private orbs. Other CircleCI functionality, including pipeline execution and orb usage in builds, is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within 30 minutes.
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.
We're seeing issues with docker on some convenience images (cimg:*) and a docker update we just pushed this morning. We are working on a fix and will let you know when we have more information. Thank you for your patience.
The fix has gone out. We will continue to monitor the situation. Sorry for any inconvenience.
Looks like everything is good. Thank you for your patience.
Some users are currently experiencing inconsistent failures when checking out. We believe this to be an issue with an upstream VCS provider and are investigating.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
GitHub have acknowledged and resolved an incident affecting their platform. https://www.githubstatus.com/incidents/vd3xqfq36rgm Users should no longer experience intermittent checkout failures.
We are currently investigating an issue affecting users attempting to log in with email and password credentials. Sign-in via GitHub or Bitbucket OAuth is not affected and remains fully operational. This issue appears to be related to an outage with a downstream authentication provider: https://status.auth0.com/
We’ve identified that the issue affecting email/password sign-ins is caused by a degradation in service from our downstream authentication provider, Auth0: https://status.auth0.com/incidents/kknl0nbdzbvx Users should still be able to sign in using GitHub or Bitbucket OAuth, which remain operational. We continue to monitor and will update as we learn more.
Our downstream authentication provider has implemented mitigation actions and is reporting a reduction in errors. We are seeing corresponding improvement in email/password login success rates. We are continuing to monitor closely to ensure stability before marking this incident resolved.
Our authentication provider has confirmed the earlier service disruption has been fully mitigated: https://status.auth0.com/incidents/kknl0nbdzbvx Email/password login functionality has been restored and is operating normally.
We are currently investigating two issues affecting CircleCI services. Users may experience slow load times on the Pipelines page and errors when attempting to view workflow details. Additionally, GitHub commit status checks may not be updating as expected for some users. Builds and jobs are continuing to run and are not impacted at this time. We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue
At approximately 16:00 UTC, we began seeing elevated load on internal data systems that serve read operations across CircleCI. This has resulted in degraded performance on the Pipelines page, difficulty loading historical workflow and pipeline data, and delays in GitHub commit status checks being posted. Write operations and job execution are unaffected — builds are queuing and running as expected. We are actively working to stabilize affected internal services and restore full read performance across the platform. We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue
We have deployed a fix to stabilize internal services that were experiencing elevated load since approximately 16:00 UTC. Affected components appear to be recovering and we are closely monitoring the situation. Users may still experience some slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to stabilize. Jobs and builds remain unaffected and continue to run as expected. We will provide our next update within 30 minutes or sooner if things change. We thank you for your patience while we continue to work to resolve this issue.
We have deployed a fix to stabilize internal services that were experiencing elevated load. Affected components are recovering and we are closely monitoring to confirm full resolution. Users may still experience some residual slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to catch up and stabilize. Jobs and builds remain unaffected and continue to run as expected. We thank you for your patience while our engineers worked to stabilize the affected services. We will provide an update within 30 minutes or earlier.
This incident has been resolved. Between approximately 16:00 UTC and 17:10 UTC, users may have experienced slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered. Jobs and builds were not impacted during this time. We apologize for the disruption and thank you for your patience.
From 11:48 to 17:16UTC some Bitbucket users may have experienced their organization not present in the CircleCI UI. Additionally some users may have encountered an issue when using `circleci config validate`. We identified the root cause of this issue and have since reverted the change. All systems for Bitbucket users are fully operational as of 17:16 UTC.
We are investigating delays of jobs. We will continue to update while investigating this.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and we are pushing out a fix. Thank you for your patience.
The issue has been identified and we are pushing out a fix. Thank you for your patience.
We're recovered and are clearing up the backlog.
This incident has been resolved.
We will update as soon as we have more information
We are currently impacted by an ongoing Github outage. We will update once we have more information.
We are starting to see some recovery and jobs are beginning to be triggered by Github again.
Customers using Github may continue to experience delays in Pipelines & UI.
Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.
We have identified delays affecting Linux and Remote Docker job execution. Customers are currently experiencing approximately 3-6 minute delays for these jobs to start due to capacity constraints in our infrastructure provider. All other compute resource classes are operating normally. We are actively mitigating this issue by routing a portion of traffic to an alternate region and continue working to restore normal service levels. - What's impacted: Linux and Remote Docker job execution - What's happening: Jobs are experiencing 3-6 minute delays starting execution due to upstream capacity constraints We will provide an update with 30 minutes. Thank you for your patience while we work to reduce these delays.
We are continuing to work on a fix for this issue.
The capacity constraints affecting Linux and Remote Docker job execution have been mitigated. Jobs are now starting within expected timeframes. We continue to monitor the situation to ensure stability. - What's impacted: Linux and Remote Docker job execution - working within normal parameters - What's happening: Service levels have returned to normal after implementing mitigation measures We will provide an update within 15 minutes or sooner if conditions change. Thank you for your patience while our engineers worked to resolve this issue.
This incident has been resolved. Thank you for your patience.
Pingoru polls Circle CI's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required