- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 11of 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 2m it lasted.
Anything that failed between 2026-04-10 10:40 UTC and 2026-04-10 10:42 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 3
- investigating
We are currently investigating this issue.
provider
- resolved
This incident has been resolved.
provider
- postmortem
Brief disruption \(~2 min\) at 6:40 AM EDT caused by a memory leak in web application pods. Pods exceeded their memory limits and were automatically restarted by the infrastructure. Our team increased the minimum pod count and enabled memory-based autoscaling at 70% threshold to prevent recurrence. Investigation into the root cause of the memory leak is ongoing.
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-9be38a1570
Is Circle still down?
No, this incident was resolved 2026-04-10 10:42 UTC. For Circle's live state, see https://down.guide/circle.
How long did it last?
2m, from 2026-04-10 10:40 UTC to 2026-04-10 10:42 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.