app.circle.so is down
Timeline · 2 updates
- investigating Sep 01, 2026, 01:59 PM UTC
We are currently investigating this issue.
- resolved Sep 01, 2026, 03:43 PM UTC
This incident has been resolved.
Circle.so had 11 outages in the last 2 years totaling 19h 0m of downtime — averaging 0.5 incidents per month.
There were 11 Circle.so outages since September 18, 2025 totaling 19h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue, which is impacting member visibility and the ability to manage your audience.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved. On January 14th, Circle experienced a brief period of degraded performance and partial unavailability. The issue was caused by increased load on our workflows application.
We are currently investigating this issue.
We were experiencing downtime affecting access to app.circle.so. This was due to a broader Cloudflare outage impacting our traffic. You can follow Cloudflare’s official updates here: https://www.cloudflarestatus.com/ The issue is resolved.
Circle services have been fully restored and communities are no longer affected. This incident was a Cloudflare-level outage, and Cloudflare is continuing to monitor the situation.
An issue with workflow execution has been identified, and a fix is being implemented.
This incident has been resolved.
We are experiencing instability on a small percentage of Android devices and are currently investigating the issue.
This incident has been resolved.
Some older Android devices couldn’t connect after new SSL certificates were installed. The new Sectigo certificate required a root certificate that older Android versions didn’t have, causing the connection failures. We fixed the issue by adding the missing intermediate certificates, and all affected Android devices are now working properly.
We’re investigating performance issues caused by the global AWS outage also impacting Amazon, Snap, Venmo, and others. See status tracker from AWS and news coverage below. Our team is standing by for resolution and will keep you informed of any changes. -AWS Status tracker: https://health.aws.amazon.com/health/status -News coverage: https://www.cnn.com/business/live-news/amazon-tech-outage-10-20-25-intl
In-app notifications and analytics features are now fully operational. We will continue to monitor closely to ensure stability.
AWS has resolved the incident. All systems are operating normally. We’ll continue to monitor for stability.