CircleCI

Minor Service Outage

Docker Jobs Operational
90 days ago
99.98 % uptime
Today
Machine Jobs Operational
90 days ago
100.0 % uptime
Today
macOS Jobs Operational
90 days ago
99.55 % uptime
Today
Windows Jobs Operational
90 days ago
100.0 % uptime
Today
Pipelines & Workflows Operational
90 days ago
99.94 % uptime
Today
CircleCI API Operational
90 days ago
99.97 % uptime
Today
CircleCI UI Operational
90 days ago
99.84 % uptime
Today
Artifacts Operational
90 days ago
100.0 % uptime
Today
Runner Operational
90 days ago
100.0 % uptime
Today
CircleCI Webhooks Operational
90 days ago
100.0 % uptime
Today
CircleCI Insights Operational
90 days ago
100.0 % uptime
Today
CircleCI Releases Operational
90 days ago
100.0 % uptime
Today
Notifications & Status Updates Operational
Billing & Account Operational
CircleCI Dependencies Operational
90 days ago
100.0 % uptime
Today
AWS Operational
Google Cloud Platform Google Cloud DNS Operational
Google Cloud Platform Google Cloud Networking Operational
Google Cloud Platform Google Cloud Storage Operational
Google Cloud Platform Google Compute Engine Operational
mailgun API Operational
mailgun Outbound Delivery Operational
mailgun SMTP Operational
OpenAI Operational
90 days ago
100.0 % uptime
Today
Auth0 User Authentication Operational
Upstream Services Partial Outage
Atlassian Bitbucket API Operational
Atlassian Bitbucket Source downloads Operational
Atlassian Bitbucket SSH Operational
Atlassian Bitbucket Webhooks Operational
Docker Hub Operational
GitHub Git Operations Operational
GitHub Pull Requests Operational
GitHub API Requests Operational
GitHub Packages Operational
GitHub Webhooks Operational
GitLab Operational
Docker Registry Operational
Docker Authentication Operational
Anthropic api.anthropic.com Partial Outage
packagecloud.io Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jul 16, 2026

No incidents reported today.

Jul 15, 2026
Resolved - 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. The same issue recurred on July 14 between 15:45 UTC and 22:50 UTC.

Delays reached up to 25 minutes on July 13 and up to 24 minutes on July 14. The medium+ and 2 X-large+ resource classes saw the longest waits. Earlier updates in this incident reported figures based on average wait times, which didn't reflect the maximum impact some customers may have experienced.

Wait times have now returned to normal. We are continuing to work with our cloud provider to add capacity ahead of the next peak period. Thank you for your patience.

Jul 15, 00:32 UTC
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.

Jul 14, 22:54 UTC
Jul 14, 2026
Postmortem - Read details
Jul 16, 01:56 UTC
Resolved - We continue to see significant VCS fetch time recovery over the last couple of hours. We're going to resolve this incident, and our engineering team will continue to monitor closely. We greatly appreciate your patience as we worked through this with our Mac infrastructure provider. Please reach out to our Support team if you have any issues.
Jul 14, 23:18 UTC
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.
Jul 14, 22:15 UTC
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.
Jul 14, 20:18 UTC
Update - 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.
Jul 14, 18:28 UTC
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.
Jul 14, 16:58 UTC
Update - 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 min continues to help: https://support.circleci.com/hc/en-us/articles/360007188574-Build-has-Hit-Timeout-Limit

Jul 14, 16:31 UTC
Update - 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
Jul 14, 15:35 UTC
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://support.circleci.com/hc/en-us/articles/360007188574-Build-has-Hit-Timeout-Limit

Jul 14, 13:59 UTC
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

Jul 13, 23:35 UTC
Update - 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.
Jul 13, 23:13 UTC
Update - We're still investigating these intermittent network issues. We'll update again shortly, we appreciate your patience.
Jul 13, 22:21 UTC
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.
Jul 13, 21:52 UTC
Postmortem - Read details
Jul 14, 22:31 UTC
Resolved - The issue where customers logging in with a Bitbucket-linked identity experienced login errors, and some customers experienced workflows that failed to start or did not update, has been resolved.

What you may still experience and need to do
- If you use Bitbucket as your login method, please log out and reauthenticate the CircleCI Bitbucket integration on your account.
- If any of your workflows are stuck or showing missing status checks, please rerun them to pick up the fix.
- If you continue to experience issues after taking these steps, please reach out to CircleCI Support.

We thank you for your patience while our team worked on implementing a fix.

Jul 14, 05:15 UTC
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

Jul 14, 04:21 UTC
Update - 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 investigate.

Next update
We will provide another update as soon as we have more information to share

Jul 14, 03:51 UTC
Update - Our team continues to investigate login errors affecting some customers using Bitbucket as their identity provider.
Jul 14, 03:29 UTC
Investigating - We are currently investigating login errors affecting some customers using Bitbucket as their identity provider.
Jul 14, 02:49 UTC
Jul 13, 2026
Resolved - We've confirmed the fix with our infrastructure provider and successful tests on our end. If customers continue to see any failed runs, please run again for a successful connection and reach out to Support if any further issues.
Jul 13, 19:40 UTC
Monitoring - Our Mac infrastructure provider has implemented a fix, we're starting to see recovery. We're monitoring and we'll update again shortly.
Jul 13, 19:29 UTC
Identified - We're working with our Mac infrastructure provider to attempt a mitigation. Will update again shortly.
Jul 13, 19:11 UTC
Investigating - We've received reports of intermittent network issues between our mac infrastructure and a VCS provider. We are investigating and will provide updates.
Jul 13, 18:55 UTC
Jul 12, 2026

No incidents reported.

Jul 11, 2026

No incidents reported.

Jul 10, 2026
Completed - We have completed the kernel upgrades across all of the infrastructure used to run Docker jobs. Our monitoring shows Docker job execution is working as normal.

During the maintenance, a small number of running jobs were canceled as machines were upgraded. These jobs will have an "Infrastructure Fail" status in the CircleCI UI. You can rerun Infrastructure Fail jobs from the UI or pushing to your VCS brach.

Please contact CircleCI support if you have any additional questions or have problems running Docker jobs.

Thank you for your patience during this maintenance.

Jul 10, 05:03 UTC
Update - We have completed migrations on several clusters. Docker jobs are continuing to run as normal with minimal disruption.

Our team will continue to monitor the rollout and update on status as the remaining clusters are upgraded.

Jul 10, 02:25 UTC
Update - The rolling upgrade is proceeding across all clusters. Our team is continuing to monitor for delays and job failures.
Jul 10, 00:29 UTC
Update - The rolling upgrades are continuing on multiple clusters. We are observing minimal impact for Docker jobs.
Jul 9, 23:02 UTC
In progress - We have rolled out kernel upgrades to a portion of our fleet.

We are seeing positive results and are proceeding with additional clusters.

Jul 9, 21:59 UTC
Scheduled - What's Happening
In order to address a High Severity CVE (CVE-2026-43499), we are rolling out an emergency security update across the entire CircleCI infrastructure used to run Docker jobs. To minimize customer impact, we are executing a rolling upgrade across each individual cluster one by one.
We expect the entire update process to complete in approximately 8 hours, and we will provide updates as individual clusters are updated.

What's Impacted
Customers running Docker jobs

What You Can Expect
Customers may see brief interruptions to Docker jobs while the updated capacity is deployed. No action is required.

Thank you for your patience while our engineers complete the rollout.

We will provide further updates as the maintenance proceeds.

Jul 9, 20:52 UTC
Jul 9, 2026
Jul 8, 2026

No incidents reported.

Jul 7, 2026

No incidents reported.

Jul 6, 2026

No incidents reported.

Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

No incidents reported.

Jul 2, 2026
Postmortem - Read details
Jul 10, 18:57 UTC
Resolved - Pipelines and UI access have fully recovered.

Please contact customer support if you have issues running builds.

This incident has been resolved.

Jul 2, 16:44 UTC
Update - Pipelines are continuing to run as normal.

We will continue monitoring for recovery.

Jul 2, 16:29 UTC
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.

Jul 2, 16:24 UTC
Update - 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.
Jul 2, 16:07 UTC
Investigating - We are currently investigating this issue.
Jul 2, 15:25 UTC