Circle CI Outage History

Started May 01, 2026, 10:51 AM UTC· resolved May 01, 2026, 11:08 AM UTC

1. investigating May 01, 2026, 10:51 AM UTC

   We are investigating the cause.

2. identified May 01, 2026, 10:58 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring May 01, 2026, 11:02 AM UTC

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

4. resolved May 01, 2026, 11:08 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 01, 2026, 10:04 AM UTC· resolved May 01, 2026, 02:02 PM UTC

1. investigating May 01, 2026, 10:04 AM UTC

   We are currently investigating

2. resolved May 01, 2026, 02:02 PM UTC

   This issue has been resolved. All data is up to date through yesterday.

Read the full incident report →

Started Apr 24, 2026, 05:25 PM UTC· resolved Apr 24, 2026, 06:36 PM UTC

1. identified Apr 24, 2026, 05:25 PM UTC

   There are build failures for Xcode 26.4.0; we have identified the issue and are currently implementing a fix.

2. monitoring Apr 24, 2026, 06:01 PM UTC

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

3. resolved Apr 24, 2026, 06:36 PM UTC

   Customers running macOS jobs on m4pro.medium and m4pro.large with the xcode:26.4.0 image experienced job rejections with the error: "Job was rejected because resource class , image xcode:26.4.0 is not a valid resource class". The issue has been resolved and affected jobs should now run normally. Customers whose jobs failed may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.

Read the full incident report →

Started Apr 18, 2026, 12:07 PM UTC· resolved Apr 18, 2026, 03:05 PM UTC

1. investigating Apr 18, 2026, 12:07 PM UTC

   Usage API data is delayed this morning. Team is investigating.

2. identified Apr 18, 2026, 01:17 PM UTC

   The Usage API issue has been identified and a fix is being implemented. We expect to the issue be resolved within a few hours.

3. resolved Apr 18, 2026, 03:05 PM UTC

   The Usage API issue has been resolved. All data is now current. Appreciate your patience.

Read the full incident report →

Started Apr 08, 2026, 01:20 PM UTC· resolved Apr 08, 2026, 08:33 PM UTC

1. identified Apr 08, 2026, 01:20 PM UTC

   We have identified an issue causing Insights workflow and job data to be delayed when requested through the Usage API. Some data for the last 24 hours may not be fully reflected while we work to process the backlog of events. Insights UI is not impacted by this issue. Thank you for your patience.

2. resolved Apr 08, 2026, 08:33 PM UTC

   The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.

Read the full incident report →

Started Apr 06, 2026, 08:33 PM UTC· resolved Apr 06, 2026, 09:12 PM UTC

1. investigating Apr 06, 2026, 08:33 PM UTC

   We are currently investigating an issue in the CircleCI UI impacting approval jobs and SSH key navigation. This is an interface-only issue and builds continue to flow as usual.

2. monitoring Apr 06, 2026, 08:43 PM UTC

   A fix has been implemented and we are monitoring the results. Thank you for your patience.

3. resolved Apr 06, 2026, 09:12 PM UTC

   This incident has been resolved.

4. postmortem Apr 07, 2026, 12:17 AM UTC

   **What happened** All modals and dialogs across the CircleCI application became invisible. They were being rendered correctly in the background, but were not visible to users. This affected approval jobs, SSH key management, and other settings pages across the app. **Root cause** The issue was introduced by an upgrade to our internal design system library. The new version added animation support to modal components using a library called Framer Motion. These animations are designed to fade modals in from invisible \(`opacity: 0`\) to visible \(`opacity: 1`\) when opened. However, the animation logic reads open/close state from a specific React context that is only available when modals are opened via a particular component \(`DialogTrigger`\). Our application manages modal state differently, passing open/close state directly via props, so that context was never populated. As a result, every modal in the app was permanently stuck in the "hidden" animation state and never transitioned to visible. **Resolution** We reverted the design system upgrade to restore the previous working version, which resolved the issue immediately. We are now working on a follow-up fix that will upgrade Framer Motion properly, by ensuring all modal components receive the required context. **Impact** The issue affected all modal dialogs across project settings, org settings, user settings, plans & payments, and other areas of the app for the duration of the incident. No data was lost or corrupted. The underlying functionality was intact, just inaccessible via the UI.

Read the full incident report →

Started Apr 02, 2026, 07:19 PM UTC· resolved Apr 03, 2026, 02:18 AM UTC

1. investigating Apr 02, 2026, 07:19 PM UTC

   We are currently investigating this issue.

2. identified Apr 02, 2026, 09:23 PM UTC

   The Usage API issue has been identified and the fix is being implemented.

3. resolved Apr 03, 2026, 02:18 AM UTC

   The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.

Read the full incident report →

Started Apr 01, 2026, 11:55 AM UTC· resolved Apr 01, 2026, 12:23 PM UTC

1. investigating Apr 01, 2026, 11:55 AM UTC

   Some pipelines may not trigger due to a high rate of API failures on one of GitHub's API endpoints. This includes some manually-triggered pipelines, some OAuth hooks and some scheduled pipelines.

2. identified Apr 01, 2026, 11:58 AM UTC

   We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.

3. monitoring Apr 01, 2026, 12:12 PM UTC

   GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.

4. resolved Apr 01, 2026, 12:23 PM UTC

   It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.

Read the full incident report →

Started Mar 18, 2026, 04:00 PM UTC· resolved Mar 18, 2026, 04:00 PM UTC

1. resolved Mar 18, 2026, 05:15 PM UTC

   On March 18, 2026, customers using workflows configured with serial groups or terminal job dependencies experienced two brief periods of disruption due to a code change. Between approximately 12:08 and 12:35 UTC, affected pipelines encountered errors when creating workflows. For pipelines created in a second window from approximately 14:23 to 14:35 UTC, GitHub status updates were not delivered for some completed jobs. Long-running workflows triggered during this window may encounter these errors after the resolution time. The underlying change was reverted in both cases. All systems have been operating normally since 14:35 UTC.

Read the full incident report →

Started Mar 16, 2026, 03:02 AM UTC· resolved Mar 16, 2026, 03:52 AM UTC

1. investigating Mar 16, 2026, 03:02 AM UTC

   We are investigating an issue where the Insights API and dashboard are returning outdated metrics for reporting windows longer than 24 hours (last 7 days, last 30 days, last 60 days, last 90 days). The last-24-hours window is unaffected and returning current data. This issue is limited to the display of aggregated metrics on Insights Page only. All pipeline pages, job runs, and builds remain fully operational and are not impacted. We will provide updates as our investigation progresses.

2. resolved Mar 16, 2026, 03:52 AM UTC

   Our engineering team has identified the root cause and has fixes prepared. Due to the nature of the data refresh process, the fix will require a deployment followed by a full refresh cycle before data is fully up to date. We expect that the data should be available within 24-36 hours. The last-24-hours reporting window continues to work normally, and all pipeline pages and job runs remain unaffected.

Read the full incident report →

Started Mar 11, 2026, 01:58 AM UTC· resolved Mar 11, 2026, 02:24 AM UTC

1. investigating Mar 11, 2026, 01:58 AM UTC

   We are investigating an issue where users are unable to view their organization's orb list on the Organization Settings page. The page may appear blank or fail to load the expected list of public and private orbs. Other CircleCI functionality, including pipeline execution and orb usage in builds, is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within 30 minutes.

2. resolved Mar 11, 2026, 02:24 AM UTC

   The issue affecting the orb list on the Organization Settings page has been resolved. Our engineers have deployed a fix and users should now be able to view their orb list as expected. Orb usage in pipelines and builds was not impacted during this incident. If you continue to experience issues, please contact CircleCI support. Thank you for your patience while we worked on resolving this issue.

Read the full incident report →

Started Mar 02, 2026, 05:59 PM UTC· resolved Mar 02, 2026, 06:21 PM UTC

1. identified Mar 02, 2026, 05:59 PM UTC

   We're seeing issues with docker on some convenience images (cimg:*) and a docker update we just pushed this morning. We are working on a fix and will let you know when we have more information. Thank you for your patience.

2. monitoring Mar 02, 2026, 06:15 PM UTC

   The fix has gone out. We will continue to monitor the situation. Sorry for any inconvenience.

3. resolved Mar 02, 2026, 06:21 PM UTC

   Looks like everything is good. Thank you for your patience.

Read the full incident report →

Started Feb 26, 2026, 10:56 PM UTC· resolved Feb 27, 2026, 12:17 AM UTC

1. identified Feb 26, 2026, 10:50 PM UTC

   Some users are currently experiencing inconsistent failures when checking out. We believe this to be an issue with an upstream VCS provider and are investigating.

2. identified Feb 26, 2026, 10:56 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 26, 2026, 10:57 PM UTC

   We are continuing to investigate this issue.

4. resolved Feb 27, 2026, 12:17 AM UTC

   GitHub have acknowledged and resolved an incident affecting their platform. https://www.githubstatus.com/incidents/vd3xqfq36rgm Users should no longer experience intermittent checkout failures.

Read the full incident report →

Started Feb 22, 2026, 05:25 PM UTC· resolved Feb 22, 2026, 07:05 PM UTC

1. investigating Feb 22, 2026, 05:25 PM UTC

   We are currently investigating an issue affecting users attempting to log in with email and password credentials. Sign-in via GitHub or Bitbucket OAuth is not affected and remains fully operational. This issue appears to be related to an outage with a downstream authentication provider: https://status.auth0.com/

2. identified Feb 22, 2026, 05:37 PM UTC

   We’ve identified that the issue affecting email/password sign-ins is caused by a degradation in service from our downstream authentication provider, Auth0: https://status.auth0.com/incidents/kknl0nbdzbvx Users should still be able to sign in using GitHub or Bitbucket OAuth, which remain operational. We continue to monitor and will update as we learn more.

3. monitoring Feb 22, 2026, 06:53 PM UTC

   Our downstream authentication provider has implemented mitigation actions and is reporting a reduction in errors. We are seeing corresponding improvement in email/password login success rates. We are continuing to monitor closely to ensure stability before marking this incident resolved.

4. resolved Feb 22, 2026, 07:05 PM UTC

   Our authentication provider has confirmed the earlier service disruption has been fully mitigated: https://status.auth0.com/incidents/kknl0nbdzbvx Email/password login functionality has been restored and is operating normally.

Read the full incident report →

Started Feb 20, 2026, 04:25 PM UTC· resolved Feb 20, 2026, 05:44 PM UTC

1. investigating Feb 20, 2026, 04:25 PM UTC

   We are currently investigating two issues affecting CircleCI services. Users may experience slow load times on the Pipelines page and errors when attempting to view workflow details. Additionally, GitHub commit status checks may not be updating as expected for some users. Builds and jobs are continuing to run and are not impacted at this time. We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue

2. investigating Feb 20, 2026, 04:56 PM UTC

   At approximately 16:00 UTC, we began seeing elevated load on internal data systems that serve read operations across CircleCI. This has resulted in degraded performance on the Pipelines page, difficulty loading historical workflow and pipeline data, and delays in GitHub commit status checks being posted. Write operations and job execution are unaffected — builds are queuing and running as expected. We are actively working to stabilize affected internal services and restore full read performance across the platform. We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue

3. identified Feb 20, 2026, 05:19 PM UTC

   We have deployed a fix to stabilize internal services that were experiencing elevated load since approximately 16:00 UTC. Affected components appear to be recovering and we are closely monitoring the situation. Users may still experience some slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to stabilize. Jobs and builds remain unaffected and continue to run as expected. We will provide our next update within 30 minutes or sooner if things change. We thank you for your patience while we continue to work to resolve this issue.

4. monitoring Feb 20, 2026, 05:31 PM UTC

   We have deployed a fix to stabilize internal services that were experiencing elevated load. Affected components are recovering and we are closely monitoring to confirm full resolution. Users may still experience some residual slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to catch up and stabilize. Jobs and builds remain unaffected and continue to run as expected. We thank you for your patience while our engineers worked to stabilize the affected services. We will provide an update within 30 minutes or earlier.

5. resolved Feb 20, 2026, 05:44 PM UTC

   This incident has been resolved. Between approximately 16:00 UTC and 17:10 UTC, users may have experienced slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered. Jobs and builds were not impacted during this time. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Started Feb 17, 2026, 10:30 AM UTC· resolved Feb 17, 2026, 10:30 AM UTC

1. resolved Feb 17, 2026, 08:22 PM UTC

   From 11:48 to 17:16UTC some Bitbucket users may have experienced their organization not present in the CircleCI UI. Additionally some users may have encountered an issue when using `circleci config validate`. We identified the root cause of this issue and have since reverted the change. All systems for Bitbucket users are fully operational as of 17:16 UTC.

Read the full incident report →

Started Feb 10, 2026, 03:21 PM UTC· resolved Feb 10, 2026, 04:13 PM UTC

1. investigating Feb 10, 2026, 03:21 PM UTC

   We are investigating delays of jobs. We will continue to update while investigating this.

2. investigating Feb 10, 2026, 03:26 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 10, 2026, 03:32 PM UTC

   We are continuing to investigate this issue.

4. identified Feb 10, 2026, 03:41 PM UTC

   The issue has been identified and we are pushing out a fix. Thank you for your patience.

5. identified Feb 10, 2026, 03:42 PM UTC

   The issue has been identified and we are pushing out a fix. Thank you for your patience.

6. monitoring Feb 10, 2026, 03:54 PM UTC

   We're recovered and are clearing up the backlog.

7. resolved Feb 10, 2026, 04:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 09, 2026, 07:48 PM UTC· resolved Feb 09, 2026, 08:25 PM UTC

1. investigating Feb 09, 2026, 07:48 PM UTC

   We will update as soon as we have more information

2. investigating Feb 09, 2026, 07:59 PM UTC

   We are currently impacted by an ongoing Github outage. We will update once we have more information.

3. monitoring Feb 09, 2026, 08:05 PM UTC

   We are starting to see some recovery and jobs are beginning to be triggered by Github again.

4. monitoring Feb 09, 2026, 08:13 PM UTC

   Customers using Github may continue to experience delays in Pipelines & UI.

5. resolved Feb 09, 2026, 08:25 PM UTC

   Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.

Read the full incident report →

Started Feb 03, 2026, 05:46 PM UTC· resolved Feb 03, 2026, 06:58 PM UTC

1. identified Feb 03, 2026, 05:46 PM UTC

   We have identified delays affecting Linux and Remote Docker job execution. Customers are currently experiencing approximately 3-6 minute delays for these jobs to start due to capacity constraints in our infrastructure provider. All other compute resource classes are operating normally. We are actively mitigating this issue by routing a portion of traffic to an alternate region and continue working to restore normal service levels. - What's impacted: Linux and Remote Docker job execution - What's happening: Jobs are experiencing 3-6 minute delays starting execution due to upstream capacity constraints We will provide an update with 30 minutes. Thank you for your patience while we work to reduce these delays.

2. identified Feb 03, 2026, 05:46 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Feb 03, 2026, 06:19 PM UTC

   The capacity constraints affecting Linux and Remote Docker job execution have been mitigated. Jobs are now starting within expected timeframes. We continue to monitor the situation to ensure stability. - What's impacted: Linux and Remote Docker job execution - working within normal parameters - What's happening: Service levels have returned to normal after implementing mitigation measures We will provide an update within 15 minutes or sooner if conditions change. Thank you for your patience while our engineers worked to resolve this issue.

4. resolved Feb 03, 2026, 06:58 PM UTC

   This incident has been resolved. Thank you for your patience.

Read the full incident report →

Started Feb 02, 2026, 08:07 PM UTC· resolved Feb 02, 2026, 10:18 PM UTC

1. investigating Feb 02, 2026, 08:07 PM UTC

   We are currently experiencing issues with email notifications across CircleCI. Build completion emails and plan-related notifications are not being delivered as expected. All other notification types, including Slack and webhook notifications, continue to function normally. Build results remain accessible through the CircleCI web interface and GitHub checks. We are actively investigating the issue with our notification delivery system and will provide an update within 30 minutes.

2. identified Feb 02, 2026, 08:34 PM UTC

   We have identified the issue affecting email notifications. Our notification delivery system is experiencing disruptions that are preventing build completion emails and plan-related notifications from being sent. We are actively working with our vendor to restore service. All other notification types, including Slack and webhook notifications, continue to function normally, and build results remain accessible through the CircleCI web interface and GitHub checks. We will provide an update within 30 minutes.

3. identified Feb 02, 2026, 09:12 PM UTC

   We continue to work with our vendor on restoring email notification delivery. Build completion emails and plan-related notifications remain impacted. All other notification types and build results through the CircleCI web interface and GitHub checks continue to function normally. We will provide an update within 30 minutes.

4. identified Feb 02, 2026, 09:48 PM UTC

   We are continuing to work with our upstream provider to restore email notification delivery. Build completion emails and plan-related notifications remain impacted. All other notification types and build results through the CircleCI web interface and GitHub checks continue to function normally. We will provide an update within 30 minutes.

5. monitoring Feb 02, 2026, 10:05 PM UTC

   Our upstream provider has resolved the issue affecting their system. We are currently monitoring email notification delivery to confirm full restoration. Build completion emails and plan-related notifications should begin flowing normally. All other notification types and build results through the CircleCI web interface and GitHub checks continue to function normally. We will provide a final update within 15 minutes.

6. monitoring Feb 02, 2026, 10:05 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Feb 02, 2026, 10:18 PM UTC

   The issue affecting email notifications has been resolved. Build completion emails and plan-related notifications are now being delivered normally. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jan 29, 2026, 07:29 PM UTC· resolved Jan 29, 2026, 07:37 PM UTC

1. identified Jan 29, 2026, 07:29 PM UTC

   We are experiencing capacity constraints affecting arm-medium, large, xlarge, 2xl, resulting in job start delays of up to 5 minutes. Current Status: - arm-medium, large, xlarge, 2xl: Experiencing delays up to 5 minutes due to capacity constraints - Docker, Mac, Windows, and Android jobs: Operating normally without delays Our engineering team is actively working to address these constraints and expand available capacity. All jobs will continue to run normally after the initial delay. We appreciate your patience as we work to resolve this issue. Next Update: Within 30 minutes or as the situation changes.

2. monitoring Jan 29, 2026, 07:35 PM UTC

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

3. monitoring Jan 29, 2026, 07:35 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 29, 2026, 07:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 12, 2026, 06:08 PM UTC· resolved Jan 12, 2026, 06:08 PM UTC

1. resolved Jan 12, 2026, 06:30 PM UTC

   We identified and resolved an issue that caused jobs to be delayed. During this period, some customers experienced longer than normal job start times while we performed database optimization work. Our team has completed the necessary tuning and service performance has returned to normal levels. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jan 08, 2026, 11:23 AM UTC· resolved Jan 09, 2026, 11:25 PM UTC

1. investigating Jan 08, 2026, 11:23 AM UTC

   A small subset of Bitbucket users are currently affected by an issue causing jobs to fail to start. This presents as a failed job that leads to a 404 page. We are currently investigating this and the affected user accounts.

2. investigating Jan 08, 2026, 01:21 PM UTC

   We have identified an issue with retrieving user identities from Bitbucket and are continuing to investigate.

3. investigating Jan 08, 2026, 03:48 PM UTC

   We are continuing to investigate and are working with upstream providers to determine a resolution.

4. investigating Jan 08, 2026, 11:29 PM UTC

   We are continuing to investigate an issue affecting Bitbucket users with a large number of projects. Jobs are failing to start for these users, and we are working to understand and mitigate the underlying rate limiting behavior. What's impacted: Bitbucket users with a large number of projects may experience job failures during the build start process. Failed jobs will present with a 404 error page. What's happening: We're continuing to investigate an issue where retrieving user identities from Bitbucket is encountering rate limiting for accounts with extensive project configurations. This prevents the user profile build process from completing, which blocks jobs from starting. What to expect: Bitbucket users with large numbers of projects may continue to experience intermittent job start failures until we can resolve the rate limiting issue. Next update: Our engineering team is continuing to investigate and work toward mitigation. We will update our users as we have new information to share or by Jan 09, 2026 - 22:00 UTC (within 24 hours). If you are impacted by this issue and have any other questions, please reach out to us via your regular support channels.

5. monitoring Jan 09, 2026, 07:05 PM UTC

   We have implemented mitigation measures to address the issue affecting Bitbucket users and are seeing significant improvement. Organizations that were previously unable to build are now building successfully. What's impacted: Bitbucket users with a large number of projects may experience job failures during the build start process. Failed jobs will present with a 404 error page. What's happening: We identified an issue where retrieving user identities from Bitbucket was encountering rate limiting for accounts with extensive project configurations. We have taken mitigating actions, which has resolved the blocking issue for most customers. What to expect: Organizations that were previously unable to build should now be able to build successfully. Individual users with access to very large numbers of repositories may still occasionally encounter rate limiting by Bitbucket during the identity retrieval process. Next update: Our engineering team is continuing to investigate the recent changes in rate limiting behavior by Bitbucket. We will update our users as we have new information to share. If you are impacted by this issue and have any questions, please reach out to us via your regular support channels.

6. resolved Jan 09, 2026, 11:25 PM UTC

   This issue has been resolved. Organizations using Bitbucket are now able to build successfully following mitigation actions we implemented earlier today. What happened: We identified an issue where retrieving user identities from Bitbucket was encountering rate limiting for accounts with extensive project configurations. This was caused by recent changes to Bitbucket's rate limiting behavior that were enforced in late December 2025. Our mitigating actions helped resolve the issue for most of the affected organizations. Current status: Organizations that were previously unable to build are now building successfully. A small number of individual users with access to very large numbers of repositories may still occasionally encounter rate limiting by Bitbucket during the identity retrieval process. These users can have another team member trigger builds as a workaround. If you continue to experience issues: Please reach out to us via your regular support channels.

Read the full incident report →

Started Dec 16, 2025, 09:17 PM UTC· resolved Dec 16, 2025, 10:12 PM UTC

1. investigating Dec 16, 2025, 09:17 PM UTC

   Customers using Machine, Linux Remote Docker, and Mac resource classes may be experiencing elevated wait times when starting jobs. We're investigating and will update again soon.

2. identified Dec 16, 2025, 09:49 PM UTC

   We've ID'd the problem and we're rolling out a fix.

3. monitoring Dec 16, 2025, 10:00 PM UTC

   Wait times for Linux, Remote Docker and Mac are starting to return to normal. We're going to keep our eye on things for just a bit longer and will update again shortly.

4. resolved Dec 16, 2025, 10:12 PM UTC

   This incident has been resolved and wait times have returned to normal. We appreciate your patience.

Read the full incident report →

Started Dec 15, 2025, 09:30 PM UTC· resolved Dec 15, 2025, 09:30 PM UTC

1. resolved Dec 15, 2025, 09:59 PM UTC

   Between 21:14 and 21:26 UTC, December 15, 2025, customers using Machine, Linux Remote Docker, and ARM resource classes experienced elevated wait times when starting jobs. Wait times reached up to 5 minutes during this period due to the delays in our infrastructure scaling to meet the demand. The issue has been resolved and wait times have returned to normal levels. Jobs are now starting within expected timeframes. No further action is required from customers, and no jobs were lost during this incident. Thank you for your patience during this brief disruption.

Read the full incident report →