Apr <var data-var='date'> 8</var>, <var data-var='time'>20:33</var> UTC Resolved - 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.Apr <var data-var='date'> 8</var>, <var data-var='time'>13:20</var> UTC Identified - We have identified an issue causing Insights workflow and job data to be delayed when requested through the Usage API. Some data for the last 24 hours may not be fully reflected while we work to process the backlog of events. Insights UI is not impacted by this issue. Thank you for your patience.

Delays in Workflow and Job data in the Usage API

Apr <var data-var='date'> 6</var>, <var data-var='time'>21:12</var> UTC Resolved - This incident has been resolved.Apr <var data-var='date'> 6</var>, <var data-var='time'>20:43</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Thank you for your patience.Apr <var data-var='date'> 6</var>, <var data-var='time'>20:33</var> UTC Investigating - We are currently investigating an issue in the CircleCI UI impacting approval jobs and SSH key navigation. This is an interface-only issue and builds continue to flow as usual.

Degradation in CircleCI UI elements

Apr <var data-var='date'> 3</var>, <var data-var='time'>02:18</var> UTC Resolved - The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.Apr <var data-var='date'> 2</var>, <var data-var='time'>21:23</var> UTC Identified - The Usage API issue has been identified and the fix is being implemented.Apr <var data-var='date'> 2</var>, <var data-var='time'>19:19</var> UTC Investigating - We are currently investigating this issue.

Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.

Apr <var data-var='date'> 1</var>, <var data-var='time'>12:23</var> UTC Resolved - It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.Apr <var data-var='date'> 1</var>, <var data-var='time'>12:12</var> UTC Monitoring - GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.Apr <var data-var='date'> 1</var>, <var data-var='time'>11:58</var> UTC Identified - We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.Apr <var data-var='date'> 1</var>, <var data-var='time'>11:55</var> UTC Investigating - Some pipelines may not trigger due to a high rate of API failures on one of GitHub's API endpoints. This includes some manually-triggered pipelines, some OAuth hooks and some scheduled pipelines.

Some pipelines not triggering due to GitHub API failures

Mar <var data-var='date'>18</var>, <var data-var='time'>16:00</var> UTC Resolved - 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.

Pipelines — Workflow Creation Errors and Missing GitHub Status Updates

Mar <var data-var='date'>16</var>, <var data-var='time'>03:52</var> UTC Resolved - 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.Mar <var data-var='date'>16</var>, <var data-var='time'>03:02</var> UTC Investigating - We are investigating an issue where the Insights API and dashboard are returning outdated metrics for reporting windows longer than 24 hours (last 7 days, last 30 days, last 60 days, last 90 days). The last-24-hours window is unaffected and returning current data. This issue is limited to the display of aggregated metrics on Insights Page only. All pipeline pages, job runs, and builds remain fully operational and are not impacted. We will provide updates as our investigation progresses.

Insights API and Dashboard displaying stale data for reporting windows greater than 24 hours

Mar <var data-var='date'>11</var>, <var data-var='time'>02:24</var> UTC Resolved - 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.Mar <var data-var='date'>11</var>, <var data-var='time'>01:58</var> UTC Investigating - 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.

Unable to view orb list on Organization Settings page

Mar <var data-var='date'> 2</var>, <var data-var='time'>18:21</var> UTC Resolved - Looks like everything is good. Thank you for your patience.Mar <var data-var='date'> 2</var>, <var data-var='time'>18:15</var> UTC Monitoring - The fix has gone out. We will continue to monitor the situation. Sorry for any inconvenience.Mar <var data-var='date'> 2</var>, <var data-var='time'>17:59</var> UTC Identified - 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.

docker not working in cimg:*

Feb <var data-var='date'>27</var>, <var data-var='time'>00:17</var> UTC Resolved - GitHub have acknowledged and resolved an incident affecting their platform. https://www.githubstatus.com/incidents/vd3xqfq36rgm Users should no longer experience intermittent checkout failures.Feb <var data-var='date'>26</var>, <var data-var='time'>22:57</var> UTC Update - We are continuing to investigate this issue.Feb <var data-var='date'>26</var>, <var data-var='time'>22:56</var> UTC Update - We are continuing to investigate this issue.Feb <var data-var='date'>26</var>, <var data-var='time'>22:50</var> UTC Identified - 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.

Degradation in some checkout steps

Feb <var data-var='date'>24</var>, <var data-var='time'>06:00</var> UTC Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>24</var>, <var data-var='time'>02:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>20</var>, <var data-var='time'>20:38</var> UTC Scheduled - Mac Cloud will be undergoing scheduled maintenance on Tuesday, February 24th from 2:00 AM to 6:00 AM UTC. During this window, m4pro.medium and m4pro.large resource classes may be affected. While we do not anticipate significant disruption, customers could experience job queuing, and any jobs running during the maintenance window may fail and be automatically retried. We will post an update once maintenance is complete.

Mac Cloud Maintenance - Tuesday, February 24th, 2:00 AM – 6:00 AM UTC

Feb <var data-var='date'>22</var>, <var data-var='time'>19:05</var> UTC Resolved - 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.Feb <var data-var='date'>22</var>, <var data-var='time'>18:53</var> UTC Monitoring - 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.Feb <var data-var='date'>22</var>, <var data-var='time'>17:37</var> UTC Identified - 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.Feb <var data-var='date'>22</var>, <var data-var='time'>17:25</var> UTC Investigating - 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/

Sign-In Issue Affecting Email/Password Logins

Feb <var data-var='date'>20</var>, <var data-var='time'>17:44</var> UTC Resolved - 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.Feb <var data-var='date'>20</var>, <var data-var='time'>17:31</var> UTC Monitoring - 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.Feb <var data-var='date'>20</var>, <var data-var='time'>17:19</var> UTC Identified - 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.Feb <var data-var='date'>20</var>, <var data-var='time'>16:56</var> UTC Update - 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 issueFeb <var data-var='date'>20</var>, <var data-var='time'>16:25</var> UTC Investigating - 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

Pipeline UI Degradation and GitHub Checks Delivery

Feb <var data-var='date'>17</var>, <var data-var='time'>10:30</var> UTC Resolved - 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.

Bitbucket Organizations unavailable in the CircleCI UI

Feb <var data-var='date'>10</var>, <var data-var='time'>16:13</var> UTC Resolved - This incident has been resolved.Feb <var data-var='date'>10</var>, <var data-var='time'>15:54</var> UTC Monitoring - We're recovered and are clearing up the backlog.Feb <var data-var='date'>10</var>, <var data-var='time'>15:42</var> UTC Update - The issue has been identified and we are pushing out a fix. Thank you for your patience.Feb <var data-var='date'>10</var>, <var data-var='time'>15:41</var> UTC Identified - The issue has been identified and we are pushing out a fix. Thank you for your patience.Feb <var data-var='date'>10</var>, <var data-var='time'>15:32</var> UTC Update - We are continuing to investigate this issue.Feb <var data-var='date'>10</var>, <var data-var='time'>15:26</var> UTC Update - We are continuing to investigate this issue.Feb <var data-var='date'>10</var>, <var data-var='time'>15:21</var> UTC Investigating - We are investigating delays of jobs. We will continue to update while investigating this.

Delay in Jobs starting

Feb <var data-var='date'> 9</var>, <var data-var='time'>20:25</var> UTC Resolved - Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.Feb <var data-var='date'> 9</var>, <var data-var='time'>20:13</var> UTC Update - Customers using Github may continue to experience delays in Pipelines & UI.Feb <var data-var='date'> 9</var>, <var data-var='time'>20:05</var> UTC Monitoring - We are starting to see some recovery and jobs are beginning to be triggered by Github again.Feb <var data-var='date'> 9</var>, <var data-var='time'>19:59</var> UTC Update - We are currently impacted by an ongoing Github outage. We will update once we have more information.Feb <var data-var='date'> 9</var>, <var data-var='time'>19:48</var> UTC Investigating - We will update as soon as we have more information

We are investigating issues with delays in pages loading

Feb <var data-var='date'> 3</var>, <var data-var='time'>18:58</var> UTC Resolved - This incident has been resolved. Thank you for your patience.Feb <var data-var='date'> 3</var>, <var data-var='time'>18:19</var> UTC Monitoring - 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.Feb <var data-var='date'> 3</var>, <var data-var='time'>17:46</var> UTC Update - We are continuing to work on a fix for this issue.Feb <var data-var='date'> 3</var>, <var data-var='time'>17:46</var> UTC Identified - 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.

Delays affecting Linux and Remote Docker jobs

Feb <var data-var='date'> 2</var>, <var data-var='time'>22:18</var> UTC Resolved - 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.Feb <var data-var='date'> 2</var>, <var data-var='time'>22:05</var> UTC Update - We are continuing to monitor for any further issues.Feb <var data-var='date'> 2</var>, <var data-var='time'>22:05</var> UTC Monitoring - 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.Feb <var data-var='date'> 2</var>, <var data-var='time'>21:48</var> UTC Update - 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.Feb <var data-var='date'> 2</var>, <var data-var='time'>21:12</var> UTC Update - 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.Feb <var data-var='date'> 2</var>, <var data-var='time'>20:34</var> UTC Identified - 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.Feb <var data-var='date'> 2</var>, <var data-var='time'>20:07</var> UTC Investigating - 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.

Email Notifications Delayed

Jan <var data-var='date'>29</var>, <var data-var='time'>19:37</var> UTC Resolved - This incident has been resolved.Jan <var data-var='date'>29</var>, <var data-var='time'>19:35</var> UTC Update - We are continuing to monitor for any further issues.Jan <var data-var='date'>29</var>, <var data-var='time'>19:35</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Jan <var data-var='date'>29</var>, <var data-var='time'>19:29</var> UTC Identified - 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.

Job start delays for arm-medium, large, xlarge, 2xl resources

Jan <var data-var='date'>27</var>, <var data-var='time'>00:00</var> UTC Completed - The scheduled maintenance has been completed.Jan <var data-var='date'>26</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'>11</var>, <var data-var='time'>23:10</var> UTC Scheduled - As part of our ongoing infrastructure improvements, we will be deprecating Mac M1 and M2 resource classes on February 16th, 2026. Ahead of the deprecation date, we will be performing 24-hour brownouts from 00:00:01 to 23:59:59 UTC, during which these resources will be unavailable. You can opt out of brownouts by disabling the setting in Organization Settings > Advanced > Enable resource class brownouts. However, please note that access to these resources will be entirely removed on February 16th, 2026, regardless of brownout settings. Please plan to transition to M4 instances (m4pro.medium and m4pro.large) ahead of the deprecation date. M4 resources will be made available to organizations on free plans starting November 10th, 2025.

Deprecation of Mac M1 and M2 resource classes

Jan <var data-var='date'>13</var>, <var data-var='time'>00:00</var> UTC Completed - The scheduled maintenance has been completed.Jan <var data-var='date'>12</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'>11</var>, <var data-var='time'>23:07</var> UTC Scheduled - As part of our ongoing infrastructure improvements, we will be deprecating Mac M1 and M2 resource classes on February 16th, 2026. Ahead of the deprecation date, we will be performing 24-hour brownouts from 00:00:01 to 23:59:59 UTC, during which these resources will be unavailable. You can opt out of brownouts by disabling the setting in Organization Settings > Advanced > Enable image brownouts. However, please note that access to these resources will be entirely removed on February 16th, 2026, regardless of brownout settings. Please plan to transition to M4 instances (m4pro.medium and m4pro.large) ahead of the deprecation date. M4 resources will be made available to organizations on free plans starting November 10th, 2025.

Jan <var data-var='date'>12</var>, <var data-var='time'>18:08</var> UTC Resolved - 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.

Delays in job start

Jan <var data-var='date'> 9</var>, <var data-var='time'>23:25</var> UTC Resolved - 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.Jan <var data-var='date'> 9</var>, <var data-var='time'>19:05</var> UTC Monitoring - 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.Jan <var data-var='date'> 8</var>, <var data-var='time'>23:29</var> UTC Update - 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.Jan <var data-var='date'> 8</var>, <var data-var='time'>15:48</var> UTC Update - We are continuing to investigate and are working with upstream providers to determine a resolution.Jan <var data-var='date'> 8</var>, <var data-var='time'>13:21</var> UTC Update - We have identified an issue with retrieving user identities from Bitbucket and are continuing to investigate.Jan <var data-var='date'> 8</var>, <var data-var='time'>11:23</var> UTC Investigating - 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.

Issues with jobs starting for certain Bitbucket users

Dec <var data-var='date'>16</var>, <var data-var='time'>22:12</var> UTC Resolved - This incident has been resolved and wait times have returned to normal. We appreciate your patience.Dec <var data-var='date'>16</var>, <var data-var='time'>22:00</var> UTC Monitoring - 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.Dec <var data-var='date'>16</var>, <var data-var='time'>21:49</var> UTC Identified - We've ID'd the problem and we're rolling out a fix.Dec <var data-var='date'>16</var>, <var data-var='time'>21:17</var> UTC Investigating - 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.

Higher wait times for Linux, Remote Docker and Mac resource classes

Dec <var data-var='date'>16</var>, <var data-var='time'>00:00</var> UTC Completed - The scheduled maintenance has been completed.Dec <var data-var='date'>15</var>, <var data-var='time'>16:43</var> UTC Update - During our maintenance, we identified an issue with the opt-out feature for the Mac M1/M2 brownouts. Organizations attempting to disable brownouts via Organization Settings > Advanced > Enable image brownouts may have found that the setting was non-functional. A fix has been deployed and the opt-out feature should now be working as expected.Dec <var data-var='date'>15</var>, <var data-var='time'>00:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Dec <var data-var='date'>11</var>, <var data-var='time'>23:01</var> UTC Scheduled - As part of our ongoing infrastructure improvements, we will be deprecating Mac M1 and M2 resource classes on February 16th, 2026. Ahead of the deprecation date, we will be performing 24-hour brownouts from 00:00:01 to 23:59:59 UTC, during which these resources will be unavailable. You can opt out of brownouts by disabling the setting in Organization Settings > Advanced > Enable image brownouts. However, please note that access to these resources will be entirely removed on February 16th, 2026, regardless of brownout settings. Please plan to transition to M4 instances (m4pro.medium and m4pro.large) ahead of the deprecation date. M4 resources will be made available to organizations on free plans starting November 10th, 2025.

Dec <var data-var='date'>15</var>, <var data-var='time'>21:30</var> UTC Resolved - 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.

Is CircleCI down?

CircleCI status is UP

Lastest published events

Delays in Workflow and Job data in the Usage API

Degradation in CircleCI UI elements

Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.

CircleCI Services, Components and Regions

Recent CircleCI events

Delays in Workflow and Job data in the Usage API

Degradation in CircleCI UI elements

Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.

Some pipelines not triggering due to GitHub API failures

Pipelines — Workflow Creation Errors and Missing GitHub Status Updates

Insights API and Dashboard displaying stale data for reporting windows greater than 24 hours

Get your FREE account now,
5 monitors included!

Is CircleCI down?

CircleCI status is UP

Lastest published events

Delays in Workflow and Job data in the Usage API

Degradation in CircleCI UI elements

Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.

CircleCI Services, Components and Regions

Recent CircleCI events

Delays in Workflow and Job data in the Usage API

Degradation in CircleCI UI elements

Usage API data for 4/1 is incomplete with multiple columns showing null values. Data prior to 4/1 is unaffected. We are investigating.

Some pipelines not triggering due to GitHub API failures

Pipelines — Workflow Creation Errors and Missing GitHub Status Updates

Insights API and Dashboard displaying stale data for reporting windows greater than 24 hours

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!