- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 27m it lasted.
Anything that failed between 2026-04-14 01:50 UTC and 2026-04-14 02:17 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
Communities experienced approximately 27 minutes of downtime starting at 9:50 PM EDT. The primary database crashed and went fully offline. Our infrastructure team performed a manual failover to a standby database in a different availability zone to restore service. The crash was caused by an AWS RDS bug that we had already escalated to AWS support. We are working with AWS to prevent recurrence and have additional monitoring in place to detect database instability earlier.
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-01a48d10aa
Is Circle still down?
No, this incident was resolved 2026-04-14 02:17 UTC. For Circle's live state, see https://down.guide/circle.
How long did it last?
27m, from 2026-04-14 01:50 UTC to 2026-04-14 02:17 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.