Live / CircleCI / Incident
CircleCI: Delays in pipelines, workflows, UI data, and notifications
CircleCI · circleci.comMajor incidentResolved2026-10-06 21:18 UTC
Public — what happened
Summary
CircleCI reported a major incident on 2026-10-06 starting at 16:00 UTC that slowed pipeline creation, job and workflow starts, data showing up in its web interface, and outgoing notifications and webhooks for its customers. The problems worsened soon after, with the company saying jobs began failing and, from 16:02 UTC, pipelines stopped working altogether before recovery began around 16:39 UTC. CircleCI said changes by its engineers improved stability and that the lingering slowdowns, at times around 40 minutes, came from a buildup of queued work, which it reported cleared by 20:13 UTC, followed by a brief queueing issue for some Docker and Linux jobs. The company said things were back to normal by 20:31 UTC, advised rerunning any jobs that failed to start, and marked the incident resolved at 21:18.
Affected
Pipelines & Workflows, Notifications & Status Updates
Timeline
- Started — 2026-10-06 16:00 UTC
- Investigating — 2026-10-06 16:00 UTC (2 updates)
- Identified — 2026-10-06 16:31 UTC (8 updates)
- Monitoring — 2026-10-06 20:31 UTC
- Resolved — 2026-10-06 21:18 UTC · 5h 18m 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.