CircleCI

Affected: macOS Jobs

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-20 15:58 UTC

   We're seeing increased wait times for some macOS jobs using the m4pro.large resource class. We're investigating and will provide another update soon. Thank you for your patience.

2. monitoring 2026-10-20 16:32 UTC

   Customers running macOS jobs on the m4pro.large resource class are still seeing increased wait times, with some jobs waiting up to 30 minutes to start. We're continuing to monitor this and will share another update shortly.

3. monitoring 2026-10-20 17:02 UTC

   Wait times for m4pro.large are still elevated due to heavy large demand. All m4pro.medium are normal. We're actively monitoring, we appreciate patience.

4. monitoring 2026-10-20 17:31 UTC

   Wait times for macOS jobs on the m4pro.large resource class are recovering. Jobs using Xcode 27.0 are now waiting about ~3.5 minutes on average, down from about ~40 minutes at the peak. Jobs using Xcode 26.6 and 26.4.1 are still working through a backlog, which is clearing. Wait...

5. resolved 2026-10-20 18:14 UTC

   Wait times for macOS jobs on the m4pro.large resource class have returned to normal. We thank you for your patience while the backlogs cleared.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 14:47 UTC

   Since approximately 14:00 UTC, customers running macOS jobs that use Xcode 26.6.0 on the M4 Pro large resource class are experiencing delays starting jobs. Wait times have reached 30 minutes or more. Thank you for your patience while our engineers investigate. We will provide...

2. identified 2026-10-14 15:17 UTC

   Delays starting macOS jobs that use Xcode 26.6.0 have recovered. Since approximately 15:11 UTC, macOS jobs that use Xcode 26.4 are experiencing delays starting, with wait times of about 30 minutes. Thank you for your patience while our engineers work to resolve this. We will...

3. resolved 2026-10-14 16:01 UTC

   Between approximately 14:00 UTC and 15:51 UTC on October 14, customers running macOS jobs that use Xcode 26.6.0 or Xcode 26.4 experienced delays starting jobs. From approximately 14:00 UTC, jobs that use Xcode 26.6.0 on the M4 Pro large resource class waited 30 minutes or more...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API, CircleCI UI

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-10-09 11:33 UTC

   There is a delay in our data infrastructure causing delays before build data and some notifications become visible. We are working on a mitigation.

2. identified 2026-10-09 13:00 UTC

   What's impacted: Customers triggering pipelines, and customers relying on outbound webhooks and email and Slack notifications. What can you expect Since 11:15 UTC: - Pipelines are still being created while this is ongoing but not yet processed, so retriggering may result in...

3. identified 2026-10-09 13:30 UTC

   Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. What's impacted: Customers triggering pipelines, and customers relying on outbound webhooks and email and Slack...

4. identified 2026-10-09 14:00 UTC

   Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. What's impacted...

5. identified 2026-10-09 14:29 UTC

   Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. What's impacted...

6. identified 2026-10-09 14:43 UTC

   Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

7. monitoring 2026-10-09 14:54 UTC

   Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

8. monitoring 2026-10-09 15:32 UTC

   Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

9. monitoring 2026-10-09 16:02 UTC

   Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

10. monitoring 2026-10-09 16:32 UTC

    Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

11. monitoring 2026-10-09 17:06 UTC

    Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

12. identified 2026-10-09 17:34 UTC

    Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

13. identified 2026-10-09 18:08 UTC

    Since 11:15 UTC, customers have experienced disruption to pipelines and notifications. Between 11:15 UTC and about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and transactional notifications (Slack and email) were not sent. Between about 13:00 UTC...

14. identified 2026-10-09 18:32 UTC

    What's changed since our last update * The CircleCI UI is about an hour behind, and up to about 90 minutes for some updates. Workflows and jobs may already have run, or may be running, even if the UI shows them as not started or does not show them at all. * Jobs that are running...

15. identified 2026-10-09 18:57 UTC

    What's changed since our last update * Jobs are starting faster. Most are now starting within about 8 minutes, down from about 15 minutes, and the longest waits have dropped from over an hour to about 45 minutes. * The CircleCI UI is beginning to catch up, but it is still...

16. identified 2026-10-09 19:29 UTC

    Since our last update, jobs are starting faster: most are now starting within about 6 minutes, down from about 8 minutes. The CircleCI UI is catching up but still about an hour behind. New pipelines are being processed as they arrive. Jobs may already have run even if the UI...

17. identified 2026-10-09 20:06 UTC

    Jobs are starting faster and fewer are failing: most jobs are now starting within about 4 minutes, down from about 6 minutes, and the longest waits have dropped from about 30 minutes to about 20 minutes. Pipelines from earlier in the incident are now being worked through. The...

18. identified 2026-10-09 21:22 UTC

    Since about 20:48 UTC, new workflows and jobs are not starting. We have temporarily paused starting new work so that our systems can catch up on work already in progress, including delayed updates to the CircleCI UI and API. Older updates are now appearing in the UI and API as...

19. identified 2026-10-09 22:09 UTC

    Since our last update, most of the pipelines that were delayed earlier in the incident have now been processed, and their workflows are queued to start. New workflows and jobs remain paused while we prepare to resume work safely. Delayed updates continue to appear in the...

20. identified 2026-10-09 22:28 UTC

    Since our last update, we have begun gradually resuming work, and some queued workflows and jobs are starting again. Most queued work is still waiting, and jobs that do start may have waited over an hour. We are increasing the rate carefully to avoid overloading our systems....

21. identified 2026-10-09 23:00 UTC

    A large number of queued workflows and jobs have started, and the CircleCI UI and API have caught up and are showing updates normally with few delays. We are continuing to work through the remaining queued work. Jobs from the queue may have waited about an hour or more to start,...

22. identified 2026-10-09 23:38 UTC

    We are still working through a significant backlog of queued workflows and jobs. Wait times are improving but they remain longer than normal and some jobs have waited over an hour. The CircleCI UI and API remain up to date. Please avoid retriggering pipelines or workflows while...

23. identified 2026-10-09 23:59 UTC

    Since our last update, the backlog of queued workflows and jobs has cleared, as of about 23:47 UTC. Workflows and jobs are now starting within seconds, and the CircleCI UI and API are up to date. We are monitoring our systems closely to make sure they remain stable. We will...

24. identified 2026-10-10 00:45 UTC

    Workflows and jobs have continued to start normally, within seconds, and the CircleCI UI and API remain up to date. Slack and email notifications delayed earlier in the incident are still being delivered. Usage charge data on the Project Usage page is stale. We are continuing to...

25. monitoring 2026-10-10 01:23 UTC

    Workflows and jobs are starting and running normally, and the CircleCI UI and API are up to date. We are continuing to monitor our systems closely to make sure they remain stable. We will provide another update by 02:00 UTC.

26. resolved 2026-10-10 02:08 UTC

    Between 11:15 UTC and 23:47 UTC on October 9, customers experienced delays and failures across pipelines, workflows and jobs, along with delays in the CircleCI UI, API and notifications. From 11:15 to about 13:00 UTC, pipelines were created but not processed, and outbound...

27. postmortem 2026-10-12 22:32 UTC

    ## Summary Between 11:15 UTC and 23:47 UTC on October 9, CircleCI customers experienced hours-long delays and failures across pipelines, workflows and jobs, along with delays in the CircleCI UI, API and notifications. * From 11:15 to 13:00 UTC, pipelines were created but not...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Machine Jobs

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-08 13:00 UTC

   Customers may be experiencing elevated wait times for machine jobs. We are working to resolve this.

2. identified 2026-10-08 13:34 UTC

   Customers using Linux machine jobs are experiencing elevated wait times, averaging about 11 minutes, with the longest waits exceeding 30 minutes on the medium, arm.medium and arm.large resource classes. Our engineers have identified the issue and are working on a fix. We will...

3. identified 2026-10-08 14:04 UTC

   Customers using Linux machine jobs are experiencing elevated wait times, averaging about 40 minutes, with the longest waits exceeding 50 minutes. Most Linux machine resource classes are affected, including medium, large, xlarge, 2xlarge and their Arm equivalents. Our engineers...

4. identified 2026-10-08 14:37 UTC

   Customers using Linux machine jobs and remote Docker are experiencing elevated wait times. Wait times have started to decrease and now average about 20 minutes, with the longest waits exceeding 40 minutes on some resource classes. Our engineers have identified the issue and are...

5. identified 2026-10-08 15:01 UTC

   A fix has been deployed and wait times are decreasing, but customers using Linux machine jobs and Remote Docker are still experiencing delays. Wait times currently average about 11 minutes, with the longest waits exceeding 35 minutes on some resource classes. We are working to...

6. identified 2026-10-08 15:31 UTC

   Wait times continue to decrease, but customers using Linux machine jobs and remote Docker are still experiencing delays. Wait times currently average about 6 minutes. The longest waits, up to about 20 minutes, are on the 2xlarge, arm.2xlarge and gpu.nvidia.small resource...

7. identified 2026-10-08 15:59 UTC

   Wait times continue to decrease, but customers using Linux machine jobs and remote Docker are still experiencing delays. Wait times currently average about 90 seconds, with the longest waits up to about 6 minutes on some resource classes. We are working to add capacity as...

8. monitoring 2026-10-08 16:09 UTC

   Wait times for customers using Linux machine jobs and remote Docker have returned to normal. We are monitoring to confirm wait times remain stable while we continue to add capacity. We will provide another update by 16:30 UTC.

9. resolved 2026-10-08 16:35 UTC

   Between 12:40 UTC and 16:00 UTC on October 8, customers using Linux machine jobs and remote Docker experienced elevated wait times. The issue has been resolved and wait times have returned to normal. We thank you for your patience while our team worked on implementing a fix.

10. postmortem 2026-10-08 17:54 UTC

    ## **Summary** Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Docker Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-07 18:54 UTC

   There is an increased wait time for jobs on Docker Gen2.

2. identified 2026-10-07 19:00 UTC

   Note: delays will be more noticeable for people running on Docker `xlarge` and above.

3. monitoring 2026-10-07 19:52 UTC

   We're still seeing spikes in task wait times but on average wait times are looking better for all Docker Gen2.

4. resolved 2026-10-07 20:05 UTC

   This incident has been resolved.

5. postmortem 2026-10-08 17:54 UTC

   ## **Summary** Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 14:27 UTC

   We are investigating a rise in infra fails for customer jobs.

2. monitoring 2026-10-07 14:44 UTC

   We're seeing signs of recovery. Docker Gen2 wait times are slightly elevated and we're monitoring.

3. resolved 2026-10-07 15:21 UTC

   This incident has been resolved.

4. postmortem 2026-10-08 17:55 UTC

   ## **Summary** Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Machine Jobs

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-07 13:40 UTC

   Customers may be experiencing elevated wait times for Machine Job Tasks, we are investigating the root cause and will update when we know more.

2. monitoring 2026-10-07 13:52 UTC

   We are seeing signs of recovery and monitoring the situation.

3. resolved 2026-10-07 14:06 UTC

   The incident has been resolved. Thank you for your patience

4. postmortem 2026-10-08 17:55 UTC

   ## **Summary** Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows, Notifications & Status Updates

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 16:00 UTC

   What's impacted Customers using CircleCI pipelines and workflows, including UI data display, outbound notifications, and outbound webhooks. What can you expect Delays in pipelines being created and in workflows and jobs starting. Job, workflow, and pipeline data may take up to...

2. investigating 2026-10-06 16:10 UTC

   Since 15:47 UTC, customers may also see failed jobs, in addition to the delays previously reported. Our engineers are continuing to investigate and mitigate the issue.

3. identified 2026-10-06 16:31 UTC

   As of 16:02 UTC, pipelines are failing entirely, so no new workflows or jobs are running at this point. This is in addition to the delays and failed jobs reported earlier. Our engineers are continuing to work on mitigating the issue, and we will share more information as soon as...

4. identified 2026-10-06 16:42 UTC

   As of 16:39 UTC, we are starting to see recovery for new pipelines and workflows being submitted, and jobs are beginning to run again. Our engineers are continuing to work on the recovery and will share more information as soon as we have it.

5. identified 2026-10-06 17:21 UTC

   While Pipelines, workflows, and jobs are running again, customers may continue to see longer than usual delays between jobs in a workflow, and outbound notifications are delayed by approximately 1 minute. Notifications and status updates to your version control system are...

6. identified 2026-10-06 18:04 UTC

   Customers continue to experience longer than usual delays between jobs in a workflow, as well as delays in outbound notifications. We thank you for your patience while our engineers continue to investigate and work on mitigating the issue. We will share another update within the...

7. identified 2026-10-06 18:55 UTC

   Customers continue to experience longer than usual delays before workflows and jobs start, in some cases up to approximately 30 minutes. This is improved from earlier in the incident, but delays remain. Delays in outbound notifications have improved. We thank you for your...

8. identified 2026-10-06 19:16 UTC

   Customers continue to experience delays. Most are now starting within approximately 20 minutes, improved from approximately 40 minutes earlier in the incident. A very small number of workflows may have waited more than 1 hour. Our engineers have made changes that have improved...

9. identified 2026-10-06 19:51 UTC

   Delays for workflows and jobs to start are continuing to decrease. Most are now starting within approximately 10 minutes, improved from approximately 40 minutes earlier in the incident. A very small number of workflows may have waited more than 1 hour. If your job failed to...

10. identified 2026-10-06 20:13 UTC

    The backlog of delayed work has been cleared, and workflows are starting again with no delays in notifications. However, customers using Docker and Linux jobs across multiple resource classes, including medium, large, and 2xlarge gen2, may now see jobs waiting in the queue for...

11. monitoring 2026-10-06 20:31 UTC

    Workflows and jobs are starting normally, and wait times for Docker and Linux jobs have returned to normal. Our engineers are continuing to monitor this issue. If your job failed to start, please rerun the job. We thank you for your patience while our engineers work on this. We...

12. resolved 2026-10-06 21:18 UTC

    Between approximately 15:30 UTC and 20:30 UTC on October 6, 2026, customers experienced delays and failures affecting pipelines, workflows, and jobs. From approximately 16:02 UTC to 16:39 UTC, pipelines were failing and no new workflows or jobs could start. After service...

13. postmortem 2026-10-07 22:08 UTC

    ## Summary On October 6, 2026, from 15:30 to 20:30 UTC, CircleCI customers experienced delays creating pipelines and starting workflows and jobs. From 15:48 to 16:38 UTC, no workflows or jobs started, and pipelines triggered from 16:02 UTC failed. Shorter, intermittent delays...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Docker Jobs

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-01 09:06 UTC

   Customers may experience delays in starting Docker Gen 2 Jobs. We are working to increase the throughput of the system to accomodate this.

2. identified 2026-10-01 09:47 UTC

   We have identified the root cause and we are actively working on a fix. Thank you for your patience.

3. identified 2026-10-01 10:13 UTC

   A fix has been rolled out and we're starting to observe recovery.

4. monitoring 2026-10-01 10:24 UTC

   We're seeing queue times return to normal levels, and continue to monitor.

5. resolved 2026-10-01 10:45 UTC

   This incident has been resolved.

6. postmortem 2026-10-09 22:36 UTC

   ## **Summary** Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Billing & Account

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-23 18:13 UTC

   Customers may experience delays in new signups and plan changes being reflected in their account.

2. resolved 2026-09-23 20:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Machine Jobs

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-21 16:22 UTC

   Customers may experience delays in starting jobs on Linux Machine. We are investigating.

2. monitoring 2026-09-21 16:48 UTC

   Task wait times for Linux Machine are returning to normal.

3. resolved 2026-09-21 17:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API, CircleCI UI

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-16 14:55 UTC

   We are investigating a delay in pipeline data becoming available. Pipelines are still running, but data about them may be delayed in the UI or API.

2. identified 2026-09-16 15:29 UTC

   We have identified the issue and are working on a remediation. Thank you for your patience.

3. identified 2026-09-16 17:34 UTC

   Pipeline data is now available as normal, with the exception of test results, which may still be delayed. We are continuing to work on this, thank you for your patience.

4. monitoring 2026-09-16 18:22 UTC

   All pipeline data is now available as normal. We will continue to monitor recovery.

5. resolved 2026-09-16 19:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI UI

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-15 14:42 UTC

   We are currently seeing a delay in pipeline data surfacing in the UI.

2. identified 2026-09-15 15:14 UTC

   We are starting to see some recovery.

3. resolved 2026-09-15 17:02 UTC

   The incident impacting pipeline data in the UI has now been resolved. We thank you for your patience while our engineers worked on reducing the delays.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-14 11:59 UTC

   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.

2. investigating 2026-09-14 12:36 UTC

   Wait times for macOS jobs are reducing and we are continuing to investigate.

3. monitoring 2026-09-14 12:48 UTC

   Our macOS hosting provider has implemented a mitigation and we have seen improved latencies. We will continue to monitor.

4. resolved 2026-09-14 12:59 UTC

   Wait times for macOS jobs are back to normal.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI UI

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-10 20:25 UTC

   A small number of customers may see errors or be unable to load the pipelines page for projects with deprecated-config warnings, when using the classic pipelines view. Customers on the new pipelines view are not affected. We’ve identified the cause and deployed a fix.

2. monitoring 2026-09-10 20:25 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-10 20:26 UTC

   This incident has been resolved. A small number of customers who created pipelines between 18:53 UTC and 19:24 UTC that contained config using deprecated config syntax will have seen their build-type jobs fail to start. Customers whose jobs or pipelines failed may rerun them.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 15:16 UTC

   We have detected network issues affecting our Mac infrastructure. We're investigating and will provide updates shortly. Customers may experience queuing during this time.

2. identified 2026-09-04 15:43 UTC

   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.

3. monitoring 2026-09-04 16:19 UTC

   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.

4. resolved 2026-09-04 16:55 UTC

   We've seen no further impact to queue times and everything has returned to normal. We appreciate your patience while we worked to resolve and monitor this issue.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API, CircleCI UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-26 15:43 UTC

   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.

2. monitoring 2026-08-26 16:04 UTC

   We have mitigated the issue with plan usage APIs and the relevant pages in the UI are loading correctly.

3. resolved 2026-08-26 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. resolved 2026-08-25 20:00 UTC

   Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI Insights

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-17 21:06 UTC

   The cause of the issue has been identified and we are at work fixing it.

2. monitoring 2026-08-17 21:36 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-17 21:37 UTC

   Insights data is good once more. Thank you for your patience.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with GitHub.com.

1. identified 2026-08-17 14:04 UTC

   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.

2. identified 2026-08-17 14:25 UTC

   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.

3. identified 2026-08-17 15:49 UTC

   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:...

4. monitoring 2026-08-17 16:22 UTC

   We have started to observe improved stability in GitHub APIs. We will continue to monitor as they recover.

5. monitoring 2026-08-17 17:01 UTC

   GitHub API error rates and latencies appear to have recovered. We will continue to monitor.

6. monitoring 2026-08-17 17:23 UTC

   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.

7. resolved 2026-08-17 19:05 UTC

   GitHub's APIs appear to be operating normally.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-15 17:00 UTC

   Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced. Some customers continued to see delays in jobs starting, along with a small number of jobs failing with...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Incident with Pull Requests and Issues.

1. identified 2026-08-12 16:33 UTC

   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...

2. resolved 2026-08-12 16:43 UTC

   The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-11 18:00 UTC

   Between 13:50 UTC and approximately 17:30 UTC on August 11, 2026, some customers experienced delays of up to an hour in pipeline status updates and in notification delivery. Between 16:40 UTC and 17:00 UTC within that same window, a small number of customers also saw newly...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-06 13:06 UTC

   Usage API data is delayed for 8/5/2026. All prior data remains available. We are investigating. Thank you for your patience.

2. identified 2026-08-06 15:06 UTC

   The issue has been identified and a fix is in progress.

3. monitoring 2026-08-06 19:33 UTC

   A fix is in place and is being monitored. Thanks for your patience.

4. resolved 2026-08-06 19:54 UTC

   The Usage API issue has been resolved. Data has been loaded for yesterday, 8/5/2026. We appreciate your patience.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI Insights

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-05 16:58 UTC

   We are seeing an issue with Insights service where the data from the last 24 hours is lagging. We are investigating.

2. investigating 2026-08-05 17:46 UTC

   We are continuing to investigate and will update as we know more.

3. identified 2026-08-05 18:25 UTC

   We have identified the issue, and are working with our upstream provider to resolve it now.

4. resolved 2026-08-05 21:01 UTC

   The upstream issue has been resolved, and the insights data from the last 24 hours has caught up. Thank you for your patience.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Machine Jobs, Windows Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-04 19:27 UTC

   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...

2. monitoring 2026-08-04 19:59 UTC

   We're starting to see queue times slowly recovering. We'll be monitoring this situation, we appreciate your patience.

3. monitoring 2026-08-04 20:33 UTC

   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.

4. monitoring 2026-08-04 21:16 UTC

   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...

5. monitoring 2026-08-04 21:46 UTC

   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...

6. monitoring 2026-08-04 22:20 UTC

   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...

7. resolved 2026-08-04 23:40 UTC

   Queue times for Android and Windows jobs have reduced significantly over the last hour. You may still notice brief, isolated queuing at times, but this is no longer at incident-level impact. This was related to capacity constraints with a third-party infrastructure provider. We...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-07-24 16:35 UTC

   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...

2. resolved 2026-07-24 17:41 UTC

   The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/yjysg0xrl67m) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Machine Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-22 19:57 UTC

   We are investigating delays in starting jobs using the gen3 resource class.

2. investigating 2026-07-22 20:43 UTC

   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.

3. investigating 2026-07-22 23:17 UTC

   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.

4. investigating 2026-07-23 00:31 UTC

   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.

5. resolved 2026-07-23 02:05 UTC

   Between 19:24 UTC on 22 July and 01:50 UTC on 23 July, customers using the gen3 preview machine (Linux VM) resource classes experienced delays and, in some cases, jobs failing to start. We have removed the gen3 resource classes while we address stability issues affecting them....

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI UI

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-07-22 06:13 UTC

   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.

2. resolved 2026-07-22 06:27 UTC

   Between 03:18 UTC and 06:04 UTC on July 22, 2026, a subset of customers were unable to access app.circleci.com. The issue has been resolved and access has returned to normal. We thank you for your patience while our team worked on implementing a fix.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows, GitHub Git Operations, GitHub API Requests

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-07-20 00:35 UTC

   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...

2. identified 2026-07-20 01:24 UTC

   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.

3. monitoring 2026-07-20 01:36 UTC

   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.

4. resolved 2026-07-20 01:45 UTC

   GitHub API error rates have recovered to normal levels. During the incident, some customers may have seen pipelines fail to start or not receive status updates. Some pipelines may be stuck in a running state. * You should re-push commits or use the UI to manually trigger...

5. postmortem 2026-07-23 21:10 UTC

   ## Summary On July 20, 2026 from 00:22 to 01:45 UTC, CircleCI customers using our GitHub integrations experienced failures running pipelines and experienced workflows getting stuck. During this incident, some pipelines triggered by users using GitHub failed to start or ran as...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-16 23:04 UTC

   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...

2. identified 2026-07-16 23:42 UTC

   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.

3. monitoring 2026-07-17 00:09 UTC

   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...

4. resolved 2026-07-17 00:26 UTC

   An incident affecting GitHub's API caused CircleCI customers to experience errors loading the web app and signing in, along with pipelines and scheduled workflows failing to start or running late. GitHub has resolved the underlying incident (https://www.githubstatus.com/) and...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Docker Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-14 22:54 UTC

   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...

2. resolved 2026-07-15 00:32 UTC

   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...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-14 02:49 UTC

   We are currently investigating login errors affecting some customers using Bitbucket as their identity provider.

2. investigating 2026-07-14 03:29 UTC

   Our team continues to investigate login errors affecting some customers using Bitbucket as their identity provider.

3. investigating 2026-07-14 03:51 UTC

   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...

4. monitoring 2026-07-14 04:21 UTC

   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...

5. resolved 2026-07-14 05:15 UTC

   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...

6. postmortem 2026-07-14 22:31 UTC

   ## Summary From 01:33 UTC to 05:18 UTC on July 14, 2026, customers with a Bitbucket-linked identity were unable to log in to CircleCI, and some customers experienced workflows that failed to start or update, due to a change in how Bitbucket's OAuth service reports account...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-13 21:52 UTC

   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.

2. investigating 2026-07-13 22:21 UTC

   We're still investigating these intermittent network issues. We'll update again shortly, we appreciate your patience.

3. investigating 2026-07-13 23:13 UTC

   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.

4. monitoring 2026-07-13 23:35 UTC

   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 -...

5. identified 2026-07-14 13:59 UTC

   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...

6. identified 2026-07-14 15:35 UTC

   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...

7. identified 2026-07-14 16:31 UTC

   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...

8. monitoring 2026-07-14 16:58 UTC

   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.

9. monitoring 2026-07-14 18:28 UTC

   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.

10. investigating 2026-07-14 20:18 UTC

    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.

11. monitoring 2026-07-14 22:15 UTC

    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.

12. resolved 2026-07-14 23:18 UTC

    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...

13. postmortem 2026-07-16 01:56 UTC

    ## Summary From 18:00 UTC on July 13, 2026 to 23:18 UTC on July 14, 2026, some customers running jobs on CircleCI's macOS fleet experienced jobs that hung or failed to progress during GitHub fetch steps. For these customers, GitHub fetch steps which would ordinarily take 1-2...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-13 18:55 UTC

   We've received reports of intermittent network issues between our mac infrastructure and a VCS provider. We are investigating and will provide updates.

2. identified 2026-07-13 19:11 UTC

   We're working with our Mac infrastructure provider to attempt a mitigation. Will update again shortly.

3. monitoring 2026-07-13 19:29 UTC

   Our Mac infrastructure provider has implemented a fix, we're starting to see recovery. We're monitoring and we'll update again shortly.

4. resolved 2026-07-13 19:40 UTC

   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.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows, CircleCI UI

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-07-02 15:25 UTC

   We are currently investigating this issue.

2. investigating 2026-07-02 16:07 UTC

   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.

3. monitoring 2026-07-02 16:24 UTC

   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...

4. monitoring 2026-07-02 16:29 UTC

   Pipelines are continuing to run as normal. We will continue monitoring for recovery.

5. resolved 2026-07-02 16:44 UTC

   Pipelines and UI access have fully recovered. Please contact customer support if you have issues running builds. This incident has been resolved.

6. postmortem 2026-07-10 18:57 UTC

   ## Summary On July 2, 2026, from 15:12 UTC to 16:44 UTC, some CircleCI customers experienced failures starting pipelines and difficulty accessing the CircleCI UI, including an inability to log in. Customers triggering pipelines via the API may also have had pipelines fail to...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI UI

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-06-29 10:23 UTC

   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.

2. investigating 2026-06-29 11:33 UTC

   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...

3. investigating 2026-06-29 11:44 UTC

   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...

4. investigating 2026-06-29 12:16 UTC

   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...

5. identified 2026-06-29 15:54 UTC

   We have identified the cause of errors accessing orgs. We are implementing a fix, and will monitor for recovery as the change rolls out.

6. monitoring 2026-06-29 16:44 UTC

   Error rates viewing orgs are recovering. We will continue to monitor to verify the fix resolves the issues.

7. resolved 2026-06-29 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-26 15:00 UTC

   We observed a surge in demand for Xcode 26.6 and have since mitigated the incident by increasing the available capacity for that Xcode version. Customers may have seen jobs queueing for ~10-15 mins.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-25 22:44 UTC

   Customers using the Usage API may not be able to access the API. Our team is investigating.

2. resolved 2026-06-25 23:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-06-24 23:13 UTC

   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.

2. identified 2026-06-24 23:33 UTC

   We have implemented a change to address the routing issues and are monitoring the results.

3. identified 2026-06-24 23:56 UTC

   Mac jobs are still seeing intermittent failures with network routing. We are working with our infrastructure provider to address the networking issues.

4. identified 2026-06-25 00:39 UTC

   We are seeing improvement in Mac job network routing. We will continue to monitor for signs of recovery.

5. monitoring 2026-06-25 01:13 UTC

   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...

6. monitoring 2026-06-25 01:22 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2026-06-25 02:20 UTC

   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.

8. investigating 2026-06-25 02:54 UTC

   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.

9. monitoring 2026-06-25 02:58 UTC

   A fix has been implemented and we are monitoring the results.

10. resolved 2026-06-25 03:06 UTC

    We are concluding this incident based on a confirmed fix with our infrastructure provider and successful tests. For any customers seeing failed runs, please run again for a successful connection.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Docker Jobs

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-23 18:34 UTC

   We are investigating reports of delays starting Docker jobs.

2. identified 2026-06-23 18:42 UTC

   We are deploying a change to mitigate this issue.

3. identified 2026-06-23 19:04 UTC

   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...

4. monitoring 2026-06-23 19:29 UTC

   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....

5. resolved 2026-06-23 19:58 UTC

   The issue where customers running Docker jobs experienced significant delays, with jobs stuck in a "preparing environment" state, has now been resolved. We thank you for your patience while our team worked on implementing a fix.

6. postmortem 2026-06-27 00:15 UTC

   ## Summary On Tuesday, June 23, 2026, our engineering team identified that a single Docker job cluster was operating below expected performance levels. Our infrastructure is organized into routing groups, each responsible for handling a specific segment of traffic, and this...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Pipelines & Workflows

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-11 21:31 UTC

   We are currently investigating this issue.

2. identified 2026-06-11 22:05 UTC

   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...

3. identified 2026-06-11 22:57 UTC

   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...

4. monitoring 2026-06-12 00:10 UTC

   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...

5. resolved 2026-06-12 00:18 UTC

   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...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 22:39 UTC

   We are investigating reports of orb publishing failing.

2. identified 2026-06-10 22:55 UTC

   We have identified the cause of the failure and are rolling out a change.

3. monitoring 2026-06-10 22:56 UTC

   The fix has been rolled out and we are monitoring for recovery.

4. resolved 2026-06-10 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: GitHub API Requests

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2026-06-10 16:30 UTC

   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

2. investigating 2026-06-10 16:30 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-10 16:32 UTC

   We are seeing signs of recovery from the GitHub API.

4. resolved 2026-06-10 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API, CircleCI UI

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-09 17:45 UTC

   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.

2. investigating 2026-06-09 18:20 UTC

   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.

3. monitoring 2026-06-09 18:32 UTC

   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

4. resolved 2026-06-09 18:43 UTC

   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...

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-07 04:20 UTC

   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...

2. resolved 2026-06-07 04:44 UTC

   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.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: Docker Jobs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 12:52 UTC

   We are noticing an increase in errors when pulling Docker images. We are investigating.

2. monitoring 2026-06-02 13:06 UTC

   We identified the issue and have deployed a fix and are now monitoring.

3. resolved 2026-06-02 13:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-01 01:04 UTC

   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.

2. investigating 2026-06-01 01:05 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-01 01:36 UTC

   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.

4. monitoring 2026-06-01 02:05 UTC

   Mac jobs are running successfully, and we are continuing to monitor the performance of our Mac fleet. Thank you for your patience.

5. resolved 2026-06-01 03:26 UTC

   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.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: macOS Jobs

Failure mode: Network, DNS, routing or connectivity failure. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-31 18:15 UTC

   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.

2. identified 2026-05-31 19:09 UTC

   We are continuing to work on resolving the networking issue for Mac jobs.

3. identified 2026-05-31 20:05 UTC

   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.

4. identified 2026-05-31 21:24 UTC

   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...

5. identified 2026-05-31 22:38 UTC

   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...

6. monitoring 2026-06-01 00:24 UTC

   We are seeing Mac jobs starting successfully and improved network connectivity to the Mac fleet. We will continue to monitor the recovery.

7. monitoring 2026-06-01 00:42 UTC

   We have processed the backlog of Mac jobs and job start times are recovering to normal parameters.

8. resolved 2026-06-01 00:45 UTC

   Mac jobs have now fully recovered. Thank you for your patience during this incident.

Excerpts are shortened. Read the full incident on CircleCI's status page.

Affected: CircleCI API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-29 14:51 UTC

   We are currently investigating this issue.

2. investigating 2026-05-29 14:57 UTC

   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.

3. resolved 2026-05-29 18:10 UTC

   The Usage API incident has been resolved.

Excerpts are shortened. Read the full incident on CircleCI's status page.