Major incident

CircleCI: Delay in data appearing in UI and API

Affected: CircleCI API, CircleCI UI

Current status of CircleCI: Operational — live CircleCI status

Timeline

1. Oct 9, 2026, 11:33 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.
2. Oct 9, 2026, 13: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.
3. Oct 9, 2026, 13: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.
4. Oct 9, 2026, 14: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.
5. Oct 9, 2026, 14:29 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.
6. Oct 9, 2026, 14:43 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.
7. Oct 9, 2026, 14:54 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.
8. Oct 9, 2026, 15:32 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.
9. Oct 9, 2026, 16:02 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.
10. Oct 9, 2026, 16:32 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.
11. Oct 9, 2026, 17:06 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.
12. Oct 9, 2026, 17:34 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.
13. Oct 9, 2026, 18:08 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.
14. Oct 9, 2026, 18:32 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.
15. Oct 9, 2026, 18:57 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.
16. Oct 9, 2026, 19:29 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.
17. Oct 9, 2026, 20:06 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.
18. Oct 9, 2026, 21:22 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.
19. Oct 9, 2026, 22:09 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.
20. Oct 9, 2026, 22:28 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.
21. Oct 9, 2026, 23: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.
22. Oct 9, 2026, 23:38 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.
23. Oct 9, 2026, 23:59 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.
24. Oct 10, 2026, 00:45 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.
25. Oct 10, 2026, 01:23 UTC
    monitoring
    Workflows and jobs are starting and running normally, and the CircleCI UI and API are up to date. We are continuing to monitor our systems closely to make sure they remain stable. We will provide another update by 02:00 UTC.
26. Oct 10, 2026, 02:08 UTC
    resolved
    Between 11:15 UTC and 23:47 UTC on October 9, customers experienced delays and failures across pipelines, workflows and jobs, along with delays in the CircleCI UI, API and notifications. From 11:15 to about 13:00 UTC, pipelines were created but not processed, and outbound webhooks and Slack and email notifications were not sent. From about 13:00 to 14:40 UTC, workflows and jobs started with delays while we worked through the backlog. From about 15:15 to 20:48 UTC, workflows and jobs started with increasing delays, of up to about an hour, and the CircleCI UI and API fell behind by up to about 2 hours. During this time, some jobs failed to start and some in-progress workflows failed. From 20:48 to about 22:10 UTC, we temporarily paused starting new workflows and jobs so our systems could recover. New pipelines were accepted and queued during this time. From about 22:10 to 23:47 UTC, queued workflows and jobs resumed and were processed. Some of them had waited up to about 2 hours. The issue has been resolved and all affected functionality has returned to normal. Usage charge data on the Project Usage page is not yet up to date and will be updated once our data backfills complete. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our engineers worked on implementing a fix.
27. Oct 12, 2026, 22:32 UTC
    postmortem
    ## Summary Between 11:15 UTC and 23:47 UTC on October 9, CircleCI customers experienced hours-long delays and failures across pipelines, workflows and jobs, along with delays in the CircleCI UI, API and notifications. * From 11:15 to 13:00 UTC, pipelines were created but not processed, and outbound webhooks and Slack and email notifications were not sent. * From 13:00 to 14:40 UTC, workflows and jobs started with delays while we worked through the backlog. * From 15:15 to 20:48 UTC, workflows and jobs started with increasing delays, of up to about an hour, and the CircleCI UI and API fell behind by up to about 2 hours. During this time, some jobs failed to start and some in-progress workflows failed. * From 20:48 to 22:10 UTC, we temporarily paused starting new workflows and jobs so our systems could recover. New pipelines were accepted and queued during this time. * From 22:10 to 23:47 UTC, queued workflows and jobs resumed and were successfully processed. Some of them had waited up to about 2 hours. * By 23:47, the incident was mitigated. The status page for this incident can be found at [October 9 - Delay in data appearing in UI and API](https://status.circleci.com/incidents/6cfhhlr4rmm0). Customers experienced a similar incident earlier in the week at [October 6 - Delays in pipelines, workflows, UI data, and notifications](https://status.circleci.com/incidents/z4hbq8h49j8c). Multiple CircleCI services use Temporal backed by Postgres as a reliable queueing mechanism, and both incidents had the same cause: the rate of writes to Temporal's Postgres instance were faster than Postgres’s transaction log could archive those writes. In both cases, this caused multi-hour delays in processing both pipelines and status notifications. We evaluated several mitigations, then paused new workflow starts so the system could recover safely, and ramped back up gradually. We then throttled work back up until our systems returned to normal. To permanently resolve the bottleneck, we have split work across multiple Temporal instances, each with its own independent database and worker clusters, and we load-balance across them. We had already scheduled infrastructure work starting the week of October 12 that would have removed this exact bottleneck and prevented these incidents. So starting 19:11 on October 9 our engineering team implemented, tested, and rolled out a simpler version of these changes within a few hours. We further added new alerting and tuned the underlying databases for better performance under high load. Customers whose jobs failed during this window may rerun them. ## Background To run customer jobs, CircleCI executes a series of steps: we accept customer pipelines; we assign jobs for those pipelines to workers; we deliver status updates for those pipelines and jobs; and we charge customers for the credits those jobs consume. Each of these steps is implemented by an independent service, with reliable queues in between. Historically we have implemented these reliable queues with RabbitMQ on top of durable storage, with exponential backoff and dead letter queues for reliability. Over the last year, we have increasingly reimplemented our reliable queues on [Temporal](https://temporal.io/), which provides far better durability and reliability guarantees over a simpler and more powerful programming model. Our build service \(which turns a pipeline config into an executable plan\), our workflow orchestrator service \(which distributes tasks onto workers\), our notification service \(which delivers status updates\), and our charging service \(which charges customers for credits\) all now use Temporal. Temporal stores the state for its workflows and activities \(called “history”\) in a database, and this is the only component in a Temporal instance that is synchronous and stateful. As a consequence, a Temporal instance’s ability to accept and execute workflows is dependent on the write rate of its backing database. We have al

Updates as published by CircleCI (original).