Circle.so incident

app.circle.so is down

Notice Resolved View vendor source →

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

Started
Apr 10, 2026, 10:40 AM UTC
Resolved
Apr 10, 2026, 10:42 AM UTC
Duration
2m
Detected by Pingoru
Apr 10, 2026, 10:40 AM UTC

Update timeline

  1. investigating Apr 10, 2026, 10:40 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 10, 2026, 10:42 AM UTC

    This incident has been resolved.

  3. 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.