Circle.so incident

app.circle.so is down

Notice Resolved View vendor source →

Circle.so experienced a notice incident on April 7, 2026, lasting 2m. The incident has been resolved; the full update timeline is below.

Started
Apr 07, 2026, 02:26 PM UTC
Resolved
Apr 07, 2026, 02:28 PM UTC
Duration
2m
Detected by Pingoru
Apr 07, 2026, 02:26 PM UTC

Update timeline

  1. investigating Apr 07, 2026, 02:26 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 07, 2026, 02:51 PM UTC

    This incident has been resolved.

  3. postmortem Apr 15, 2026, 08: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.