Update timeline
- investigating Apr 10, 2026, 10:40 AM UTC
We are currently investigating this issue.
- resolved Apr 10, 2026, 10:42 AM UTC
This incident has been resolved.
- postmortem Apr 15, 2026, 08:11 PM UTC
Brief disruption \(~2 min\) at 6:40 AM EDT caused by a memory leak in web application pods. Pods exceeded their memory limits and were automatically restarted by the infrastructure. Our team increased the minimum pod count and enabled memory-based autoscaling at 70% threshold to prevent recurrence. Investigation into the root cause of the memory leak is ongoing.
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
Start monitoring Circle.so for free
5 free monitors · No credit card required