← Back to CircleCI's check readings
We started checking CircleCI on August 20, 2026, which is 54 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when CircleCI reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what CircleCI's own status page declared. Below it, any public chatter we saw about CircleCI and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what CircleCI's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about CircleCI in the last 24 hours, which is not evidence that nothing is wrong.
CircleCI's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is CircleCI's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention CircleCI next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
CircleCI's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delay in data appearing in UI and APIPartial outage
Oct 9, 2026, 11:33 AM UTC to Oct 10, 2026, 2:08 AM UTC (14h 36m)resolved
their latest update (Oct 10, 2026, 2:08 AM UTC): 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 webhoo…
Elevated wait times for machine jobsMinor incident
Oct 8, 2026, 1:00 PM UTC to Oct 8, 2026, 4:35 PM UTC (3h 35m)postmortem published
their latest update (Oct 8, 2026, 5:54 PM UTC): ## **Summary**
Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was…
Increased task wait times for Docker Gen2Minor incident
Oct 7, 2026, 6:54 PM UTC to Oct 7, 2026, 8:05 PM UTC (1h 11m)postmortem published
their latest update (Oct 8, 2026, 5:54 PM UTC): ## **Summary**
Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was…
Elevated level of infra fails on customer jobsMinor incident
Oct 7, 2026, 2:27 PM UTC to Oct 7, 2026, 3:21 PM UTC (54 min)postmortem published
their latest update (Oct 8, 2026, 5:55 PM UTC): ## **Summary**
Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was…
Delay on starting Machine Job TasksMinor incident
Oct 7, 2026, 1:40 PM UTC to Oct 7, 2026, 2:06 PM UTC (26 min)postmortem published
their latest update (Oct 8, 2026, 5:55 PM UTC): ## **Summary**
Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was…
Delays in pipelines, workflows, UI data, and notificationsPartial outage
Oct 6, 2026, 4:00 PM UTC to Oct 6, 2026, 9:18 PM UTC (5h 18m)postmortem published
their latest update (Oct 7, 2026, 10:08 PM UTC): ## Summary
On October 6, 2026, from 15:30 to 20:30 UTC, CircleCI customers experienced delays creating pipelines and starting workflows and jobs. From 15:48 to 16:38 UTC, no workflows or jobs started, and pipelines triggered from 16:02 UTC failed. Shorter, intermittent delays be…
Delays starting Gen 2 Docker JobsMinor incident
Oct 1, 2026, 9:06 AM UTC to Oct 1, 2026, 10:45 AM UTC (1h 39m)postmortem published
their latest update (Oct 9, 2026, 10:36 PM UTC): ## **Summary**
Between October 1 and October 8, 2026, CircleCI customers experienced five separate incidents in which jobs waited longer than normal to start, or failed to start. Three of the incidents were driven by limited instance availability from our cloud provider. One was…
Delays in processing new signups and plan changesAll systems operational
Sep 23, 2026, 6:13 PM UTC to Sep 23, 2026, 8:06 PM UTC (1h 53m)resolved
their latest update (Sep 23, 2026, 8:06 PM UTC): This incident has been resolved.
Delays starting Linux Machine jobsMinor incident
Sep 21, 2026, 4:22 PM UTC to Sep 21, 2026, 5:09 PM UTC (47 min)resolved
their latest update (Sep 21, 2026, 5:09 PM UTC): This incident has been resolved.
Customers may experience delays in UI updatesMinor incident
Sep 16, 2026, 2:55 PM UTC to Sep 16, 2026, 7:30 PM UTC (4h 35m)resolved
their latest update (Sep 16, 2026, 7:30 PM UTC): This incident has been resolved.
Showing the 10 most recent of 66 incidents CircleCI has declared in the history we hold.
These entries are CircleCI's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
CircleCI's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.