- Level
- confirmed
- Worst impact
- Degraded
- Components
- CircleCI API
- Down Index
- 23of 100
What to do
Check whether you use CircleCI CircleCI API. 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 7h 13m it lasted.
Anything that failed between 2026-04-08 13:20 UTC and 2026-04-08 20:33 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 2
- identified
We have identified an issue causing Insights workflow and job data to be delayed when requested through the Usage API. Some data for the last 24 hours may not be fully reflected while we work to process the backlog of events. Insights UI is not impacted by this issue. Thank you for your patience.
provider
- resolved
The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.
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-c732ad446e
Is CircleCI still down?
No, this incident was resolved 2026-04-08 20:33 UTC. For CircleCI's live state, see https://down.guide/circleci.
How long did it last?
7h 13m, from 2026-04-08 13:20 UTC to 2026-04-08 20:33 UTC, by the times CircleCI posted.
What was affected?
CircleCI named CircleCI API.
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.