CircleCI Outage History
Daily status observations, past incidents, and reported issue history for CircleCI.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 44% | 25 | 14 |
| July 2026 | 22.6% | 31 | 24 |
| June 2026 | 20% | 30 | 24 |
| May 2026 | 20% | 5 | 4 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Insight data is currently delayed
Started:
CircleCI Insights
identified
The cause of the issue has been identified and we are at work fixing it.
GitHub Incidents impacting CircleCI functionality
Started:
monitoring
Some of GitHub's APIs are still degraded, resulting in a small number of failures relating to commit status updates and hook processing. We will continue to do our best to mitigate these effects.
monitoring
GitHub API error rates and latencies appear to have recovered. We will continue to monitor.
monitoring
We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover.
identified
We are continuing to see high error rates on GitHub's APIs and reduced webhook traffic. Customers using GitHub as their VCS may experience impact to their CircleCI platform experience as a result. This is directly linked to the incident GitHub is experiencing: https://www.githubstatus.com/incidents/zkxwbgr0cnmx
We will provide updates as more information becomes available.
identified
We are continuing to see high error rates on GitHub APIs and reduced webhook traffic.
We will continue to provide updates as more information becomes available.
identified
GitHub has reported an incident that is impacting CircleCI pipeline triggering and logging in: https://www.githubstatus.com/incidents/zkxwbgr0cnmx
Jobs that are in flights are running, but status reporting to GitHub Pull Requests may fail.
GitHub service degradation may impact customers using GitHub
Started:
identified
GitHub is currently experiencing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h). Customers who use GitHub as their VCS may experience impact to their CircleCI platform experience as a result, impacting checkout and workflows.
We will provide another update as we have more information to share. Thank you for your patience.
Usage API data delayed for 8/5
Started:
monitoring
A fix is in place and is being monitored. Thanks for your patience.
identified
The issue has been identified and a fix is in progress.
investigating
Usage API data is delayed for 8/5/2026. All prior data remains available. We are investigating. Thank you for your patience.
Insights service data is lagging
Started:
identified
We have identified the issue, and are working with our upstream provider to resolve it now.
investigating
We are continuing to investigate and will update as we know more.
investigating
We are seeing an issue with Insights service where the data from the last 24 hours is lagging. We are investigating.
Increased Job Queue Times: Windows, Android, and GPU
Started:
monitoring
Queue times for both Android and Windows jobs, affected by capacity constraints with our third-party infrastructure provider, have been recovering significantly for the last half hour. We're continuing to monitor for a bit longer to confirm they return to normal levels. We appreciate your patience.
monitoring
Queue times for both Android and Windows jobs continue to be volatile, with sharp swings up and down. This remains related to capacity constraints with our third-party infrastructure provider. Our team will continue to monitor and provide updates at least every 30 minutes. We appreciate your patience.
monitoring
Queue times for both Android and Windows jobs, which had been recovering, have started to rise again. This continues to be related to capacity constraints with our third-party infrastructure provider. We'll continue to monitor and provide updates at least every 30 minutes. We appreciate your patience.
monitoring
Queue times continue to gradually recover with our third-party infrastructure provider, though we've seen a slight uptick in the last 30 mins. We're keeping an eye on this and will keep you updated as things get back to normal. Again, thank you for your patience.
monitoring
We're starting to see queue times slowly recovering. We'll be monitoring this situation, we appreciate your patience.
investigating
We are experiencing increased queue times for Windows, Android, and GPU jobs due to capacity constraints with a third-party infrastructure provider. Jobs will continue to be processed but may take longer than usual to start. Thank you for your patience while our engineers work to resolve this.
July 2026
GitHub service degradation may impact customers using GitHub
Started:
identified
GitHub is currently experiencing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m). Customers who use GitHub as their VCS may experience impact to their CircleCI platform experience as a result, impacting checkout and workflows.
We will provide another update as we have more information to share. Thank you for your patience.
Delays in starting jobs using the gen3 resource class
Started:
investigating
We have identified the issue and are working with our provider to resolve the availability of gen 3 resources. Gen 1 and Gen 2 are both fully operational.
investigating
We are continuing to investigate elevated wait times affecting customers using gen3 machine executors. Affected jobs may take longer than usual to start. We will provide another update as soon as we have more information to share.
investigating
We are continuing to investigate elevated wait times affecting customers using gen3 machine executors. Affected jobs may take longer than usual to start. We will provide another update as soon as we have more information to share.
investigating
We are investigating delays in starting jobs using the gen3 resource class.
Errors loading app.circleci.com
Started:
monitoring
A subset of customers may have experienced errors loading app.circleci.com starting at 03:18 UTC. A fix has been deployed and we are monitoring for full recovery.
Thank you for your patience while our engineers confirm recovery. We will provide another update shortly.
Errors with GitHub APIs delaying workflows
Started:
monitoring
We are seeing signs of recovery from the GitHub API.
We will stay in a monitoring state to verify that the API error rate has recovered.
identified
We are also seeing errors processing push event webhooks due to the upstream API outage.
Users may need to retry pipelines for these push events.
identified
We have identified an issue with GitHub API requests that may cause some customers to see workflows stuck in a running state or workflows fail to start.
GitHub has reported incidents on the APIs
https://www.githubstatus.com/incidents/ph5nns5y4gxj
https://www.githubstatus.com/incidents/8vfyvq16hzh9
We are monitoring the stability of GitHub APIs and will update this page as more information is available.
Errors accessing CircleCI and delays starting pipelines and scheduled workflows
Started:
monitoring
What's happening
The upstream incident affecting GitHub has been mitigated and is now being monitored on GitHub's side. You can follow GitHub's status at https://www.githubstatus.com/.
What can you expect
Access to the CircleCI web app, sign-in, and pipeline and workflow processing are returning to normal. You may still see intermittent errors or delayed scheduled pipelines and workflows as systems stabilize. Thank you for your patience while we monitor for full recovery.
identified
We are continuing to see high failure rates from GitHub APIs which are impacting login and workflow processing.
We will continue to monitor the GitHub API for recovery.
investigating
We're investigating an issue where customers may see errors loading the CircleCI web app and signing in, along with pipelines and scheduled workflows failing to start or running late. This is related to an ongoing incident affecting GitHub. You can follow GitHub's status at https://www.githubstatus.com/incidents/gxycch3076xk. Our engineers are actively investigating.
We will provide another update as soon as we have more information to share.
Delays starting jobs on Docker (Gen 2) resource classes
Started:
identified
On July 13 between 15:30 UTC and 22:40 UTC, we experienced delays starting jobs on Docker (Gen 2) resource classes due to capacity constraints from our cloud provider. Delays reached up to approximately 1 minute 48 seconds.
We are continuing to experience these delays again since approximately 15:45 UTC. So far, delays have reached up to approximately 1 minute 19 seconds.
We are working with our cloud provider to add capacity and will update this incident as the situation changes.
Login issues for some Bitbucket users
Started:
monitoring
What's impacted
Some customers logging in with a Bitbucket-linked identity were affected. This may also have included customers logging in with GitHub who have a linked Bitbucket identity on their account. Some customers also experienced workflows that were not starting or updating.
What can you expect
A fix has been deployed. We are monitoring the situation to confirm full recovery.
Next update
We will provide an update if anything changes
investigating
What's impacted
Some customers logging in with a Bitbucket-linked identity are affected. This may also include customers logging in with GitHub but have a linked Bitbucket identity on their account. Additionally, some customers are experiencing workflows that are not starting or updating.
What can you expect
Affected customers may see login errors. Some customers may also notice workflows that fail to start or do not update as expected. Thank you for your patience while our engineers investi...
investigating
Our team continues to investigate login errors affecting some customers using Bitbucket as their identity provider.
investigating
We are currently investigating login errors affecting some customers using Bitbucket as their identity provider.
Issues with network routing for Mac jobs
Started:
monitoring
Our Mac infrastructure provider has shifted more traffic to working network providers and we're starting to see significant recovery again in VCS fetch times. As always, our engineering team will continue to monitor this closely and we'll provide another update soon.
investigating
We're starting to see VCS fetch times rising again. Our engineering team is actively investigating and working with our Mac infrastructure provider to resolve this. Again, we appreciate your patience.
monitoring
We're continuing to see slow, progressive recovery in VCS fetch times. We're going to continuing monitoring and update again soon. We appreciate your patience.
monitoring
Our Mac infrastructure provider has shifted the inbound routes and we are seeing recovery in VCS fetch times. We will be continuing to monitor this issue over the next few hours. We'll update again soon.
identified
We've identified the issue as some inbound routes from the affected VCS provider causing significantly lower available bandwidth which is negatively impacting repo fetch times. We're working with our Mac infrastructure provider to attempt to shift inbound traffic to a different route, however this process may take an extended period of time to complete. We will continue to provide updates as they become available.
As we've shared in previous updates, increasing the no_output_timeout to 15-20...
identified
Our Mac infrastructure provider is testing changes to their network configuration in an effort to isolate the source of the issue. We're actively validating whether this resolves the impact and will follow up with another update soon. In the meantime, increasing the no_output_timeout to 15-20 min continues to help: https://support.circleci.com/hc/en-us/articles/360007188574-Build-has-Hit-Timeout-Limit
identified
Unfortunately there are still some customers that may be experiencing jobs that hang or fail to progress during Github fetch steps due to ongoing intermittent networking issues with our Mac infrastructure provider. Our engineers are actively working with them to resolve this. We appreciate your patience.
In the meantime, we've seen success with increasing the no_output_timeout to 15 - 20 min to allow more time for Github fetches. This can be done by following this community guide: https://su...
monitoring
We've identified the issue. Some customers may experience jobs that hang or fail to progress during Github fetch steps due to intermittent networking issues. Our engineers are actively monitoring.
In the meantime, we've seen success with increasing the no_output_timeout to 15 - 20 min to allow more time for Github fetches. This can be done by following this community guide: https://support.circleci.com/hc/en-us/articles/360007188574-Build-has-Hit-Timeout-Limit
investigating
We've been able to reproduce the issue, but it still appears to be very much intermittent. We're continuing to work with our Mac infrastructure provider to help diagnose the issue. We'll update again soon.
investigating
We're still investigating these intermittent network issues. We'll update again shortly, we appreciate your patience.
investigating
We're received some reports of intermittent network issues between our mac infrastructure and a VCS provider again. We are investigating and will provide updates.
Issues with network routing for Mac jobs
Started:
monitoring
Our Mac infrastructure provider has implemented a fix, we're starting to see recovery. We're monitoring and we'll update again shortly.
identified
We're working with our Mac infrastructure provider to attempt a mitigation. Will update again shortly.
investigating
We've received reports of intermittent network issues between our mac infrastructure and a VCS provider. We are investigating and will provide updates.
Outage impacting web experience and pipelines starting
Started:
monitoring
Pipelines are continuing to run as normal.
We will continue monitoring for recovery.
monitoring
We have identified a source of increased system load which caused failures processing API requests.
We have mitigated the issue and jobs are now running as expected and UI access has recovered.
Some pipelines may have failed or failed to start. Resubmitting should correct these issues.
We are continuing to monitor to ensure recovery.
investigating
We are investigating an issue that may cause some customers to be redirected to a login page and prevents some pipelines from starting. Thank you for your patience as we continue our mitigation of this issue.
investigating
We are currently investigating this issue.
June 2026
Some customers are unable to access their organizations
Started:
monitoring
Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues.
identified
We have identified the cause of errors accessing orgs. We are implementing a fix, and will monitor for recovery as the change rolls out.
investigating
We are continuing to investigate reports that some customers cannot access their organizations in CircleCI.
Our investigation continues to point to an authorization issue between CircleCI and GitHub. Some affected users have received a 403 from GitHub indicating the resource is SAML protected and the OAuth token may not be authorized.
We previously shared re-authenticating as a potential workaround. We have since received reports that this didn't restore access for all affected customers, s...
investigating
We are still investigating reports that some customers cannot access their organizations in CircleCI.
Early findings suggest the problem may be related to GitHub authorization, where affected users receive a 403 from GitHub indicating the resource is SAML protected and the OAuth token may not be authorized.
We have not yet confirmed this as the root cause. As a potential workaround, some users may be able to restore access by performing a re-authentication: https://support.circleci.com/hc/e...
investigating
We are continuing to investigate reports that some customers are unable to access their organizations in CircleCI. Those affected may see errors when loading their organizations.
Our engineering team are still working to identify the cause. We will share another update as soon as we have more information.
investigating
We are investigating reports that some customers are unable to access their organizations in CircleCI. Those affected may see errors when loading their organizations.
Our engineering team is actively investigating.
Investigating — Usage API Not Available
Started:
investigating
Customers using the Usage API may not be able to access the API. Our team is investigating.
Issues with network routing for Mac jobs
Started:
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Due to continued reports of intermittent failures and a lack of sustained improvement while in monitoring status, this incident is elevated back to investigating to escalate with our infrastructure provider.
monitoring
We are continuing to monitor. We still observe a low percentage of intermittent failures. The failure rate is trending down as we continue to monitor. We advise customers to contact CircleCI Support if they see a change in degraded services and increased failure rate.
monitoring
We are continuing to monitor for any further issues.
monitoring
Our team is moving this incident to Monitoring status based on significant improvement seen in our tests and low error rate. We are seeing improvement in network routing for Mac jobs and are actively engaged with our infrastructure provider. If your Mac jobs experience network-related failures or degraded service please reach out to CircleCI support.
identified
We are seeing improvement in Mac job network routing.
We will continue to monitor for signs of recovery.
identified
Mac jobs are still seeing intermittent failures with network routing.
We are working with our infrastructure provider to address the networking issues.
identified
We have implemented a change to address the routing issues and are monitoring the results.
investigating
What's happening
Our engineers are investigating network routing issues for some Mac jobs.
What's impacted
Mac jobs that make outbound requests, including checking out from GitHub.
Delays starting Docker jobs
Started:
monitoring
What's happening
Our engineers have deployed a fix and we are observing the job backlog clearing. Docker jobs are now starting normally.
What's impacted
Customers who submitted Docker jobs during the incident window may still see some jobs completing with elevated queue times. Newly submitted jobs should be starting at normal times.
What can you expect
Docker job startup times are returning to normal. Thank you for your patience while our engineers resolved this issue.
We are monitoring th...
identified
What's impacted
Customers running Docker jobs. Affected jobs are queuing rather than starting, resulting in elevated wait times.
What can you expect
Docker jobs may remain stuck in "preparing environment" for an extended period. Our engineers have identified the cause and are actively working to restore normal job startup times. Thank you for your patience while our team deploys a fix.
Next update
We will provide another update as soon as more information is available
identified
We are deploying a change to mitigate this issue.
investigating
We are investigating reports of delays starting Docker jobs.
Elevated API Error Rates for Bitbucket Users
Started:
investigating
What's happening
We are investigating an issue we believe is related to an ongoing incident with Atlassian Bitbucket's authentication service. We are actively monitoring Bitbucket's status.
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Thank you for your patience while our engineers investigate.
We will provide an update as soon as w...
Issue authenticating only Bitbucket users
Started:
monitoring
What's happening
Atlassian Bitbucket has moved their OAuth service incident to monitoring. You can follow their status at https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitbucket as their login provider may also be unable to authenticate to CircleCI.
Thank ...
identified
What's happening
Atlassian Bitbucket has acknowledged an incident affecting their OAuth service, which is the cause of the errors our customers are experiencing. The status of their incident is available at: https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitb...
identified
What's happening
We are investigating an issue we believe is related to an ongoing incident with Atlassian Bitbucket's authentication service. We are actively monitoring Bitbucket's status.
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Thank you for your patience while our engineers investigate.
We will provide an update as soon as w...
investigating
We are currently investigating this issue.
Issues publishing orbs
Started:
monitoring
The fix has been rolled out and we are monitoring for recovery.
identified
We have identified the cause of the failure and are rolling out a change.
investigating
We are investigating reports of orb publishing failing.
Incident with GitHub APIs
Started:
monitoring
We are seeing signs of recovery from the GitHub API.
investigating
We are continuing to investigate this issue.
investigating
Some users may have seen delays or missing commit statuses on GitHub PRs due to an ongoing GitHub API incident.
We are continuing to process builds as normal.
We will provide further updates as we get more information
Increased 500 Errors on Pipeline and Workflow API Endpoints and UI
Started:
monitoring
A fix has been deployed for the 500 errors customers were experiencing on the pipeline values and workflow API endpoints and in the UI. Engineers are monitoring the change. Jobs running are not impacted
investigating
Our engineers are continuing to investigate the 500 errors customers are experiencing on the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs currently running are not impacted.
investigating
Some customers are experiencing 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI.
Engineers are actively investigating.
macOS jobs failing to start
Started:
identified
We have identified an issue causing macOS jobs to fail to start and are working to restore service. This impacts customers running macOS jobs across all resource classes.
Thank you for your patience while our engineers work to resolve this. We will provide another update within 30 minutes.
Errors on Cloud Docker Pulls
Started:
monitoring
We identified the issue and have deployed a fix and are now monitoring.
investigating
We are noticing an increase in errors when pulling Docker images. We are investigating.
Mac jobs failing to start
Started:
monitoring
Mac jobs are running successfully, and we are continuing to monitor the performance of our Mac fleet.
Thank you for your patience.
monitoring
We are seeing Mac jobs starting successfully and improved network connectivity to the Mac fleet, however our infrastructure provider is continuing to experience a DDoS attack.
We will continue to monitor the recovery while bringing additional capacity to our platform.
investigating
We are continuing to investigate this issue.
investigating
Mac jobs are continuing to experience failures. Our infrastructure provider is continuing to report that they are experiencing a DDoS attack causing high network latency and packet loss for our Mac fleet. We are working to bring up additional capacity to restore service.
May 2026
Mac jobs failing to start
Started:
monitoring
We have processed the backlog of Mac jobs and job start times are recovering to normal parameters.
monitoring
We are seeing Mac jobs starting successfully and improved network connectivity to the Mac fleet. We will continue to monitor the recovery.
identified
Mac jobs are continuing to experience failures. Our infrastructure provider is reporting they are experiencing a DDoS attack causing high network latency and packet loss for our Mac fleet. We are working to bring up additional capacity to restore service.
We will continue to update as more information is available.
identified
We are continuing to investigate failures with Mac jobs starting due to high network latency and packet loss. Our engineers remain engaged with our infrastructure provider to restore service.
We will provide another update within the hour, or sooner if circumstances change. We thank you for your patience while our engineers work to resolve this.
identified
We are still seeing failures with Mac jobs starting due to high network latency and packet loss. We will continue to update as we have more information on a resolution.
identified
We are continuing to work on resolving the networking issue for Mac jobs.
identified
We have identified a network outage that is preventing Mac jobs from starting. This include m4pro.medium and m4pro.large resource types.
We are working with our infrastructure provider to restore service.
We will update this incident as we work to resolve the issue.
Usage API data delayed for 5/28
Started:
investigating
We've identified a small number of duplicate records in the Usage API data. Data is available, but may be inaccurate. We continue to investigate.
investigating
We are currently investigating this issue.
Elevated 429 errors pulling from maven central
Started:
monitoring
We're monitoring to verify that rate limited jobs are recovering.
investigating
Jobs pulling dependencies from maven central are experiencing increased 429 errors due to maven central rate limits.
We are investigating the issue and working to identify mitigations for customer jobs.
Some Pipelines are being lost
Started:
monitoring
The rollback was successful. Pipelines are flowing normally again. Monitoring for a bit.
investigating
We are continuing to investigate this issue.
investigating
We are having an issue with some pipelines being lost. We are rolling back the affected service, and will share more information when we have it.
GitHub incident with Pull Requests
Started:
monitoring
We are continuing to monitor for any further issues.
monitoring
GitHub is reporting a major incident for degraded pull request availability. This does not impact running CircleCI builds for newly created pull requests or push events.
Jobs using Xcode 14.3.1 on m4pro.large are delayed.
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating the cause.
Usage API data is delayed for data from yesterday, 4/30. All prior data is available. We are investigating.
Started:
investigating
We are currently investigating
April 2026
Build failures Xcode 26.4.0
Started:
monitoring
A fix has been implemented and we are monitoring the results.
identified
There are build failures for Xcode 26.4.0; we have identified the issue and are currently implementing a fix.
Usage API data delayed this morning
Started:
identified
The Usage API issue has been identified and a fix is being implemented. We expect to the issue be resolved within a few hours.
investigating
Usage API data is delayed this morning. Team is investigating.
Delays in Workflow and Job data in the Usage API
Started:
identified
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.
Degradation in CircleCI UI elements
Started:
monitoring
A fix has been implemented and we are monitoring the results. Thank you for your patience.
investigating
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.
Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.
Started:
identified
The Usage API issue has been identified and the fix is being implemented.
investigating
We are currently investigating this issue.
Some pipelines not triggering due to GitHub API failures
Started:
identified
We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.
investigating
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.
March 2026
Insights API and Dashboard displaying stale data for reporting windows greater than 24 hours
Started:
investigating
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.