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 2m it lasted.

  Anything that failed between 2026-04-07 14:26 UTC and 2026-04-07 14:28 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

1. investigatingApr 7, 2026, 2:26 PM UTC

   We are currently investigating this issue.

   provider

2. resolvedApr 7, 2026, 2:28 PM UTC

   This incident has been resolved.

   provider

3. postmortemApr 15, 2026, 8:19 PM UTC

   Communities experienced approximately 2 minutes of degraded availability starting at 10:26 AM EDT. The issue was caused by application servers returning 500 errors due to a combination of unoptimized database queries and a framework regression that affected health checks, causing pods to cycle. Multiple engineering teams responded and deployed a fix. Root cause: A Rails 8.1 upgrade changed how internal state was managed between requests, causing intermittent crashes. This was compounded by high-frequency queries that increased database load. Both issues have been patched.

   provider

Corrections

None so far.

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