Resolved after 2 minutes, on April 10, 2026.
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.
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.
Your product runs on more than Circle.so
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services