- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 15of 100
What to do
Check whether your product depends on CircleCI. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 17m it lasted.
Anything that failed between 2026-08-11 17:42 UTC and 2026-08-11 18:00 UTC may need a replay.Subscribe to CircleCI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=circleci works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from CircleCI 1
- resolved
Between 13:50 UTC and approximately 17:30 UTC on August 11, 2026, some customers experienced delays of up to an hour in pipeline status updates and in notification delivery. Between 16:40 UTC and 17:00 UTC within that same window, a small number of customers also saw newly created pipelines fail to process, appearing in an errored state in the UI and API. The issue has been resolved and all affected functionality has returned to normal. Customers whose pipelines errored during that window can retrigger them. We thank you for your patience while our team worked on implementing a fix.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b3b9acb972
Is CircleCI still down?
No, this incident was resolved 2026-08-11 18:00 UTC. For CircleCI's live state, see https://down.guide/circleci.
How long did it last?
17m, from 2026-08-11 17:42 UTC to 2026-08-11 18:00 UTC, by the times CircleCI posted.
What caused it?
CircleCI hasn't published a root cause. If it does, it shows here.
Where does this come from?
CircleCI's official status page, https://status.circleci.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.