Looking for an update now? Check the current status, or follow CircleCI for future changes.
48.2%of 56 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
50%
30
15
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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 provide another update by 15:45 UTC.
investigating
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 another update by 15:30 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.
identified
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 monitor our systems closely and will provide another update by 01:15 UTC.
identified
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 provide another update by 00:30 UTC.
identified
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 the backlog clears, as this may create duplicates. We will provide another update by 00:00 UTC.
identified
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, and some Linux jobs are waiting up to about 10 minutes for capacity.
Please continue to avoid retriggering while queued work continues to process.
We will provide another update by 23:30 UTC.
identified
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. Delayed updates continue to appear in the CircleCI UI and API.
Please continue to avoid retriggering pipelines or workflows, as this may create duplicates as queued work resumes.
We will provide another update by 23:00 UTC.
identified
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 CircleCI UI and API.
Please continue to avoid retriggering pipelines or workflows, as this may create duplicates once work resumes.
We will provide another update by 22:30 UTC.
identified
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 this backlog clears. New pipelines are still being accepted and queued
Please avoid retriggering pipelines or workflows during this time, as this may create duplicates once work resumes.
We will provide another update by 22:00 UTC.
identified
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 CircleCI UI is still behind, and some older updates may take longer to appear. Jobs may already have run even if the UI does not show them yet, so please avoid retriggering workflows that don't appear in the UI.
We will provide another update by 20:30 UTC.
identified
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 does not show them yet, so please avoid retriggering workflows that don't appear in the UI.
We will provide another update by 20:00 UTC.
identified
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 behind. 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.
* Pipelines are being processed faster, but new pipelines are still delayed.
Still ongoing
* Some workflows and jobs are still failing.
* Please avoid retriggering workflows that don't yet appear in the UI, as this may create duplicates.
* Usage charge data on the Project Usage page is stale.
Next update
We will provide another update by 19:30 UTC.
identified
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 are starting faster. Most are now starting within about 15 minutes, down from about 28 minutes, though some are still waiting over an hour.
* New pipelines are increasingly delayed.
* Some workflows are still failing. Workflows that could not be processed in time are being marked as failed.
* Please avoid retriggering workflows that don't yet appear in the UI, as this may create duplicates.
Still ongoing:
Usage charge data on the Project Usage page is stale.
Next update
We will provide another update by 19:00 UTC.
identified
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog. Since about 15:15 UTC, workflows and jobs have again been starting with delays.
What’s impacted
Customers triggering pipelines and running workflows and jobs, customers viewing pipelines, workflows and jobs in the CircleCI UI, and customers viewing usage data on the Project Usage page.
What to expect
- Since about 17:00 UTC, we are seeing an increase in delays. Most jobs are now taking about 25 minutes to start, and some are waiting up to about an hour.
- Since about 17:15 UTC, some in-progress workflows have failed and a small number of jobs are failing to start.
- New pipelines are being queued and are taking longer to start.
- The CircleCI UI is more than an hour behind. New workflows and status changes may take that long to appear.
- Please avoid retriggering workflows that don't yet appear in the UI, as this may create duplicates.
- Usage charge data on the Project Usage page is currently stale.
Our engineers continue to work to resolve the issue at hand.
Next update
We will provide another update by 18:30 UTC.
identified
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog. Since about 15:15 UTC, workflows and jobs have again been starting with delays.
What’s impacted
Customers triggering pipelines and running workflows and jobs, customers viewing pipelines, workflows and jobs in the CircleCI UI, and customers viewing usage data on the Project Usage page.
What can you expect
- Since about 17:00 UTC, delays have increased significantly. Most jobs are now taking about 12 minutes to start, and some are waiting up to about 30 minutes.
- Since about 17:15 UTC, some jobs are failing to start.
- Pipelines are being processed more slowly, so some may take longer to start.
- The CircleCI UI is more than an hour behind. New workflows and status changes may take that long to appear.
- Please avoid retriggering workflows that don’t yet appear in the UI, as this may create duplicates.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to resolve this.
Next update
We will provide another update by 18:00 UTC.
monitoring
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog. Since about 15:15 UTC, workflows and jobs have again been starting with delays.
What’s impacted
Customers running workflows and jobs, customers viewing pipelines, workflows and jobs in the CircleCI UI, and customers viewing usage data on the Project Usage page.
What can you expect
- Delays starting workflows and jobs are holding steady. Most jobs are starting within about 4 minutes, and some are waiting up to about 8 minutes, down from about 25 minutes.
- The CircleCI UI remains about 20 minutes behind on average, and some updates are taking longer. New workflows and status changes may take that long to appear.
- Please avoid retriggering workflows that don’t yet appear in the UI, as this may create duplicates.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to reduce these delays.
Next update
We will provide another update by 17:30 UTC.
monitoring
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog. Since about 15:15 UTC, workflows and jobs have again been starting with delays.
What's impacted
Customers running workflows and jobs, customers viewing pipelines, workflows and jobs in the CircleCI UI, and customers viewing usage data on the Project Usage page.
What can you expect
- Delays starting workflows and jobs have stopped increasing and are beginning to ease. Most jobs are starting within about 4 minutes, and some are waiting up to about 25 minutes.
- The CircleCI UI is now about 20 minutes behind, down from about 30 minutes. New workflows and status changes may take that long to appear.
- Please avoid retriggering workflows that don't yet appear in the UI, as this may create duplicates.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to reduce these delays.
Next update
We will provide another update by 17:00 UTC.
monitoring
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog.
What's impacted
Customers running workflows and jobs, customers viewing pipelines, workflows and jobs in the CircleCI UI, and customers viewing usage data on the Project Usage page.
What can you expect
- Since about 15:15 UTC, workflows and jobs have been starting with increasing delays. Most jobs are currently starting within about 4 minutes, and some are waiting up to about 20 minutes.
- The CircleCI UI remains about 30 minutes behind on average, and some updates are taking longer. New workflows and status changes may take that long to appear.
- Please avoid retriggering workflows that don't yet appear in the UI, as this may create duplicates.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to reduce these delays.
Next update
We will provide another update by 16:30 UTC.
monitoring
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog.
What's impacted
Customers viewing pipelines, workflows and jobs in the CircleCI UI, and customers viewing usage data on the Project Usage page.
What can you expect
- Workflows and jobs are running on time.
- The CircleCI UI is about 30 minutes behind. New workflows and status changes may take that long to appear.
- Our engineers are actively working to speed up processing so the UI can catch up.
- Please avoid retriggering workflows that don't yet appear in the UI, as this may create duplicates.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to reduce this delay.
Next update
We will provide another update by 16:00 UTC.
monitoring
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog.
What’s impacted
Customers running workflows and jobs, and customers viewing usage data on the Project Usage page.
What can you expect
- The backlog of pipelines and workflows from the incident has cleared.
- Since about 14:45 UTC, most workflows and jobs are starting within about 15 seconds, and start times are continuing to return to normal.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers monitor the recovery.
Next update
We will provide another update by 15:20 UTC.
identified
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 and 14:40 UTC, workflows and jobs started with delays while we worked through the backlog.
What’s impacted
Customers running workflows and jobs, and customers viewing usage data on the Project Usage page.
What can you expect
- The backlog of workflows from pipelines triggered during the incident cleared at about 14:40 UTC.
- Most jobs are now starting within about 30 seconds, and some are waiting up to about 3 minutes.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers continue to work on the underlying issue.
Next update
We will provide another update by 15:10 UTC.
identified
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
Customers running workflows and jobs, and customers viewing usage data on the Project Usage page.
What can you expect
- Delays starting workflows and jobs are improving. Most jobs are now starting within about 3 minutes, down from about 10 minutes at 13:50 UTC.
- Some workflows from pipelines triggered during the incident are still waiting up to about 40 minutes to start.
- Working through the backlog is taking slightly longer than expected. We now expect to clear it by about 14:45 UTC.
- Workflows from pipelines triggered during the incident are still waiting to start, so retriggering may result in duplicate workflows.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to resolve this.
Next update
We will provide another update by 15:00 UTC.
identified
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
Customers running workflows and jobs, and customers viewing usage data on the Project Usage page.
What can you expect
- Pipelines are being processed again, including those triggered during the incident.
- Since about 13:25 UTC, workflows and jobs have been starting with increasing delays as we work through the backlog. Most jobs are currently starting within about 10 minutes, and some are waiting up to about 25 minutes.
- We expect to work through this backlog by about 14:35 UTC.
- Workflows from pipelines triggered during the incident are still waiting to start, so retriggering may result in duplicate workflows.
- Usage charge data on the Project Usage page is currently stale.
Thank you for your patience while our engineers work to resolve this.
Next update
We will provide another update by 14:30 UTC.
identified
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 notifications.
What can you expect:
- Since about 13:00 UTC, pipelines are being processed again and jobs are starting.
- Most jobs are currently starting within about 4 minutes, and some are waiting up to about 10 minutes. Pipelines triggered during the incident are still being processed and may take longer to start.
- Outbound webhooks and notifications have resumed.
- Pipelines are still being processed from the backlog, so retriggering may result in duplicate pipelines.
Thank you for your patience while our engineers work to resolve this.
Next update:
We will provide another update by 14:00 UTC.
identified
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 duplicate pipelines.
- Outbound webhooks and transactional notifications (Slack and email) are not being sent.
- Pipeline statuses may not be visible.
- Usage charge data on the Project Usage page will be stale.
Thank you for your patience while our engineers work to resolve this.
Next update:
We will provide another update by 13:30 UTC.
identified
There is a delay in our data infrastructure causing delays before build data and some notifications become visible. We are working on a mitigation.
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.
identified
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 quickly as possible. We will provide another update by 16:30 UTC.
identified
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 classes. We are working to add capacity as quickly as possible. We will provide another update by 16:00 UTC.
identified
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 add capacity as quickly as possible. We will provide another update by 15:30 UTC.
identified
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 working on a fix. We will provide another update by 15:00 UTC.
identified
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 have identified the issue and are working on a fix. We will provide another update by 14:30 UTC.
identified
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 provide another update by 14:00 UTC.
identified
Customers may be experiencing elevated wait times for machine jobs. We are working to resolve this.
Pipelines & WorkflowsNotifications & Status Updates
monitoring
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 will share another update within the next 30 minutes, or sooner if more information becomes available.
identified
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 few minutes before they start. Our engineers are continuing to work on mitigating 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 will share another update within the next 30 minutes, or sooner if more information becomes available.
identified
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 start, please rerun the job. Delays in outbound notifications have improved.
The remaining delay is due to a backlog of work that built up during the incident, and that backlog has reduced by more than half. We expect the backlog to be cleared in approximately 15 minutes. We will share another update once it has cleared, or within the next 30 minutes at the latest.
identified
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 service stability, and the remaining delay is due to a backlog of work that built up during the incident. The backlog is decreasing, and we are focused on clearing it faster. We will share more information as progress continues.
We thank you for your patience while our engineers work through the backlog. We will share another update within the next 30 minutes, or sooner if more information becomes available.
identified
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 patience while our engineers continue to work toward restoring normal job start times. We will share another update within the next 30 minutes, or sooner if more information becomes available.
identified
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 next 30 minutes, or sooner if more information becomes available.
identified
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 beginning to go out again.
Our engineers are continuing to work toward a full recovery.
identified
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.
identified
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 we have it.
investigating
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.
investigating
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 15 minutes to appear in the UI. Outbound notifications and webhooks are delayed by up to 1 minute.
Next update
We will provide another update within 30 minutes or as we have more information to share.
All pipeline data is now available as normal. We will continue to monitor recovery.
identified
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.
identified
We have identified the issue and are working on a remediation. Thank you for your patience.
investigating
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.
Legacy Incident Archive
42 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Elevated API Error Rates for Bitbucket Users
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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 disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Thank you for your patience while our engineers investigate.
We will provide an update as soon as w...
Issue authenticating only Bitbucket users
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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 disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitbucket as their login provider may also be unable to authenticate to CircleCI.
Thank ...
identified
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 impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitb...
identified
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 disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Thank you for your patience while our engineers investigate.
We will provide an update as soon as w...
investigating
We are currently investigating this issue.
Issues publishing orbs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been rolled out and we are monitoring for recovery.
identified
We have identified the cause of the failure and are rolling out a change.
investigating
We are investigating reports of orb publishing failing.
Incident with GitHub APIs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are seeing signs of recovery from the GitHub API.
investigating
We are continuing to investigate this issue.
investigating
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
Increased 500 Errors on Pipeline and Workflow API Endpoints and UI
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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
investigating
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.
investigating
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.
macOS jobs failing to start
majorSource not attested
Last archived state: resolved
View archived record details
identified
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 30 minutes.
Errors on Cloud Docker Pulls
Source not attested
Last archived state: resolved
View archived record details
monitoring
We identified the issue and have deployed a fix and are now monitoring.
investigating
We are noticing an increase in errors when pulling Docker images. We are investigating.
Mac jobs failing to start
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Mac jobs are running successfully, and we are continuing to monitor the performance of our Mac fleet.
Thank you for your patience.
monitoring
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.
investigating
We are continuing to investigate this issue.
investigating
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.
May 2026
Mac jobs failing to start
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have processed the backlog of Mac jobs and job start times are recovering to normal parameters.
monitoring
We are seeing Mac jobs starting successfully and improved network connectivity to the Mac fleet. We will continue to monitor the recovery.
identified
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 update as more information is available.
identified
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 thank you for your patience while our engineers work to resolve this.
identified
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.
identified
We are continuing to work on resolving the networking issue for Mac jobs.
identified
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.
Usage API data delayed for 5/28
Source not attested
Last archived state: resolved
View archived record details
investigating
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.
