Circle: app.circle.so is down

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 1h 43m it lasted.
Anything that failed between 2026-04-30 18:00 UTC and 2026-04-30 19:43 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.

investigatingApr 30, 2026, 6:00 PM UTC
We are currently investigating this issue.
provider
resolvedApr 30, 2026, 7:43 PM UTC
This incident has been resolved.
provider
postmortemApr 30, 2026, 7:43 PM UTC
Some users experienced an issue where app.circle.so was unavailable. This was caused by the Redis cluster reaching 100% CPU due to a large volume of workflow jobs being re-enqueued. We identified the root cause, scaled down the background deployment pods to relieve the load, and restored service within approximately 3 minutes. We are continuing to investigate and address the underlying issue.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Circle still down?

No, this incident was resolved 2026-04-30 19:43 UTC. For Circle's live state, see https://down.guide/circle.

How long did it last?

1h 43m, from 2026-04-30 18:00 UTC to 2026-04-30 19:43 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.