Live / CircleCI / Incident
CircleCI: Delay in data appearing in UI and API
CircleCI · circleci.comMajor incidentResolved2026-10-10 02:08 UTC
Public — what happened
Summary
CircleCI said a problem in its data systems, beginning around 11:15 UTC on October 9, 2026, delayed build information and notifications, affecting customers who trigger pipelines or depend on webhooks, email and Slack alerts. According to the company, pipelines were accepted but sat unprocessed and notifications went unsent until about 13:00 UTC, after which jobs began running again with growing waits while a backlog was worked through, clearing at about 14:40 UTC. CircleCI later reported that its web interface was running roughly 30 minutes behind, that job start delays returned after about 15:15 UTC, and that usage charge figures were out of date, while advising customers not to retrigger work to avoid duplicates. The company did not name a specific cause in these updates, and the incident was marked resolved at 02:08 on October 10.
Affected
CircleCI API, CircleCI UI
Timeline
- Started — 2026-10-09 11:33 UTC
- Identified — 2026-10-09 11:33 UTC (6 updates)
- Monitoring — 2026-10-09 14:54 UTC (5 updates)
- Identified — 2026-10-09 17:34 UTC (13 updates)
- Monitoring — 2026-10-10 01:23 UTC
- Resolved — 2026-10-10 02:08 UTC · 14h 36m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach CircleCI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for CircleCI: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the CircleCI report →
More from CircleCI
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.