- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Circle. 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 44m it lasted.
Anything that failed between 2026-09-01 14:06 UTC and 2026-09-01 14:50 UTC may need a replay.Subscribe to Circle's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=circle works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Circle 2
- investigating
We are currently investigating this issue.
provider
- resolved
Earlier today, we experienced a brief service disruption from 9:59–10:50 AM ET during a scheduled security update. Service has been fully restored, and we've put safeguards in place to prevent this from happening again. We apologize for any inconvenience.
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-4a246b4b3a
Is Circle still down?
No, this incident was resolved 2026-09-01 14:50 UTC. For Circle's live state, see https://down.guide/circle.
How long did it last?
44m, from 2026-09-01 14:06 UTC to 2026-09-01 14:50 UTC, by the times Circle posted.
What caused it?
Circle hasn't published a root cause. If it does, it shows here.
Where does this come from?
Circle's official status page, https://status.circle.so, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.