Looking for an update now? Check the current status, or follow CircleCI for future changes.
48.2%of 56 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
50%
30
15
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.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Wait times for macOS jobs are reducing and we are continuing to investigate.
investigating
Due to increased network errors and latencies we are seeing increased wait times for macOS jobs. We are investigating this with our macOS hosting provider.
Our Mac infrastructure provider has applied a fix to this networking issue and we're seeing queue times return to normal. We're going to continue keeping an eye on things for a little while longer. We'll update again shortly.
identified
We've identified the networking issue with our Mac infrastructure provider, and are working with them to resolve the issue. We're starting to see some recovery, but we expect customers may still see some queueing. We'll update again shortly.
investigating
We have detected network issues affecting our Mac infrastructure. We're investigating and will provide updates shortly. Customers may experience queuing during this time.
August 2026
Intermittent errors when viewing plan usage UIs or calling plan usage APIs
We have mitigated the issue with plan usage APIs and the relevant pages in the UI are loading correctly.
identified
Customers may experience intermittent errors when viewing plan usage UIs or calling plan usage APIs. We have identified the issue and we are actively working to mitigate these errors.
Legacy Incident Archive
42 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Errors accessing CircleCI and delays starting pipelines and scheduled workflows
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
criticalSource not attested
Last archived state: resolved
View archived record details
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
majorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
majorSource not attested
Last archived state: resolved
View archived record details
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
majorSource not attested
Last archived state: resolved
View archived record details
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.
