Circle.so Outage History

Some users experienced an issue where app.circle.so was unavailable. This was caused by the Redis cluster reaching 100% CPU due to a large volume of workflow jobs being re-enqueued. We identified the root cause, scaled down the background deployment pods to relieve the load, and restored service within approximately 3 minutes. We are continuing to investigate and address the underlying issue.

Mobile API endpoints experienced intermittent 500 errors starting at 6:57 AM EDT on April 9. This was caused by a Rails 8.1 regression where a change in how ActiveSupport::CurrentAttributes managed state between requests caused crashes in OpenTelemetry instrumentation. Affected workers returned errors on every request, including health checks, causing pods to restart repeatedly. The root cause was identified at 7:45 AM EDT, and a fix was deployed. This issue should have had a status page entry since it impacted customers using the mobile app.

Search functionality was degraded starting at approximately 6:52 PM EDT on April 14. The issue was caused by Elasticsearch cluster degradation. An incident report was filed internally. This issue should have had a status page entry since customers reported broken search. Customers checking [status.circle.so](http://status.circle.so/) saw 'All Systems Operational' during this period.