Update timeline
- investigating Apr 07, 2026, 02:26 PM UTC
We are currently investigating this issue.
- resolved Apr 07, 2026, 02:51 PM UTC
This incident has been resolved.
- 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.
Looking to track Circle.so downtime and outages?
Pingoru polls Circle.so's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Circle.so reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Circle.so alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required