New Multi-region uptime checks and custom-domain status pages

Delays in pipelines, workflows, UI data, and notifications

Major Impact Resolved Duration: 5h 19m October 6, 2026
View the provider incident record →

Current answer

CircleCI experienced a major incident: Delays in pipelines, workflows, UI data, and notifications. ServiceAlert observed recovery on Oct 6, 2026.

Official CircleCI status page Current CircleCI status ServiceAlert observed status change:

Looking for an update now? Check the current status, or follow CircleCI for future changes.

Incident Lifecycle

Investigating Investigating Identified Identified Identified Identified Identified Identified Identified Identified Monitoring
Affected Components
Pipelines & Workflows Notifications & Status Updates

Incident Timeline

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.
Oct 6, 2026 at 8:31 PM UTC
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.
Oct 6, 2026 at 8:13 PM UTC
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.
Oct 6, 2026 at 7:51 PM UTC
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.
Oct 6, 2026 at 7:16 PM UTC
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.
Oct 6, 2026 at 6:55 PM UTC
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.
Oct 6, 2026 at 6:04 PM UTC
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.
Oct 6, 2026 at 5:21 PM UTC
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.
Oct 6, 2026 at 4:42 PM UTC
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.
Oct 6, 2026 at 4:31 PM UTC
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.
Oct 6, 2026 at 4:10 PM UTC
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.
Oct 6, 2026 at 4:00 PM UTC
Was your business affected by this CircleCI outage?
Follow CircleCI and route available status alerts to email or a team channel.