Circle Outage History
61 incidents recorded over the last 365 days, 56 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Circle Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Delays with notifications and background processingWe experienced a higher-than-usual volume of content being created on the platform, which temporarily increased the load on our background processing systems and resulted in some delays. | 5h 31m | Resolved |
| Oct 5, 2026 | app.circle.so is down#### Summary Circle application experienced an incident between 5:44 and 5:57 AM EST We’re sorry for the disruption #### What happened \(high level\) The incident was caused by a missing configuration in the… | 13 min | Resolved |
| Oct 3, 2026 | app.circle.so is downThis incident has been resolved. | 4 min | Resolved |
| Sep 1, 2026 | app.circle.so is downEarlier today, we experienced a brief service disruption from 9:59–10:50 AM ET during a scheduled security update. Service has been fully restored, and we've put safeguards in place to prevent this from happening again… | 51 min | Resolved |
| Aug 27, 2026 | app.circle.so is downThis incident has been resolved. | 1 min | Resolved |
| Aug 20, 2026 | app.circle.so is downThis incident has been resolved. | 0 min | Resolved |
| Aug 20, 2026 | app.circle.so is downWe are currently investigating this issue. | 23 min | Resolved |
| Aug 19, 2026 | app.circle.so is downThis incident has been resolved. | 16 min | Resolved |
| Jul 19, 2026 | Server maintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| Jun 29, 2026 | Scheduled maintenance (extended)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 29, 2026 | Scheduled maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 28, 2026 | Workflows stuck in "In progress" status## Delays in Asynchronous Actions and Workflows **Issue Summary** On May 28, 2026, we experienced an incident that caused delays in asynchronous actions and automated workflows. **Timeline \(UTC\)** * **11:29** –… | 3h 28m | Resolved |
| May 22, 2026 | app.circle.so is downThis incident has been resolved. | 2 min | Resolved |
| May 20, 2026 | app.circle.so is downThis incident has been resolved. | 1 min | Resolved |
| May 9, 2026 | app.circle.so is downThis incident has been resolved. | 0 min | Resolved |
| Apr 30, 2026 | app.circle.so is downSome 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… | 1h 42m | Resolved |
| Apr 30, 2026 | app.circle.so is downThis incident has been resolved. | 9 min | Resolved |
| Apr 30, 2026 | app.circle.so is downThis incident has been resolved. | 3 min | Resolved |
| Apr 30, 2026 | app.circle.so is downThis incident has been resolved. | 1 min | Resolved |
| Apr 19, 2026 | app.circle.so is downThis incident has been resolved. | 1h 41m | Resolved |
| Apr 19, 2026 | app.circle.so is downThis incident has been resolved. | 13 min | Resolved |
| Apr 19, 2026 | Server maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Apr 17, 2026 | app.circle.so is downThis incident has been resolved. | 1 min | Resolved |
| Apr 15, 2026 | Mobile API endpoint errorsMobile 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… | -8899 min | Resolved |
| Apr 14, 2026 | Elasticsearch DegradationSearch 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… | 0 min | Resolved |
| Apr 14, 2026 | app.circle.so is downCommunities experienced approximately 19 minutes of downtime starting at 12:17 AM EDT. The database crashed due to an out-of-memory error at the infrastructure level, a known AWS RDS bug. Our team raised a second… | 0 min | Resolved |
| Apr 14, 2026 | app.circle.so is downCommunities experienced approximately 27 minutes of downtime starting at 9:50 PM EDT. The primary database crashed and went fully offline. Our infrastructure team performed a manual failover to a standby database in a… | 26 min | Resolved |
| Apr 13, 2026 | app.circle.so is downCommunities experienced approximately 6 minutes of degraded availability at 5:14 PM EDT. This was a continuation of database load from the previous incident caused by an unoptimized query. The fix was deployed shortly… | 5 min | Resolved |
| Apr 13, 2026 | app.circle.so is downCommunities experienced approximately 3 minutes of degraded availability at 4:21 PM EDT. The issue was caused by an unoptimized database query in the live streams feature making 71 calls per second to the primary… | 3 min | Resolved |
| Apr 10, 2026 | app.circle.so is downBrief 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… | 2 min | Resolved |
| Apr 9, 2026 | app.circle.so is downBrief disruption \(~2 min\) at 7:21 AM EDT. This was the final occurrence of an intermittent issue caused by a Rails 8.1 framework regression. The root cause was identified 24 minutes later and a permanent fix was… | 2 min | Resolved |
| Apr 9, 2026 | app.circle.so is downBrief disruption \(~4 min\) caused by an intermittent application error related to a framework upgrade. The root cause was identified later that morning and a fix was deployed. | 3 min | Resolved |
| Apr 8, 2026 | app.circle.so is downCommunities experienced approximately 4 minutes of downtime starting at 5:47 PM EDT. The issue was caused by an unexpected database crash triggered by an AWS infrastructure bug in the RDS service. Our team identified… | 2 min | Resolved |
| Apr 8, 2026 | app.circle.so is downBrief connectivity disruption lasting approximately 1 minute. Services recovered automatically. | 0 min | Resolved |
| Apr 7, 2026 | app.circle.so is downCommunities experienced approximately 2 minutes of degraded availability starting at 10:26 AM EDT. The issue was caused by application servers returning 500 errors due to a combination of unoptimized database queries… | 2 min | Resolved |
| Apr 5, 2026 | app.circle.so is downBrief disruption detected at 11:05 PM EDT. Services recovered quickly. The status page remained open longer than the actual impact due to a delay in manual close. Actual customer-facing downtime was likely under 5… | 9 min | Resolved |
| Apr 4, 2026 | app.circle.so is downBrief disruption \(~1 min\) caused by an intermittent application error related to a recent framework upgrade. This did not represent sustained downtime. The root cause \(Rails 8.1 regression\) was identified and… | 24h 1m | Resolved |
| Apr 4, 2026 | app.circle.so is downBrief disruption detected at 11:05 PM EDT. Services recovered quickly. The status page remained open longer than the actual impact due to a delay in manual close. Actual customer-facing downtime was likely under 5… | 0 min | Resolved |
| Apr 3, 2026 | app.circle.so is downBrief connectivity disruption lasting under 1 minute. Services recovered automatically. No customer action needed. | 0 min | Resolved |
| Apr 3, 2026 | app.circle.so is downBrief connectivity disruption lasting approximately 1 minute. Pingdom monitoring detected the issue and services recovered automatically. No customer action needed. | 1 min | Resolved |
| Mar 27, 2026 | app.circle.so is downThis incident has been resolved. | 1 min | Resolved |
| Mar 26, 2026 | app.circle.so is downThis incident has been resolved. | 11 min | Resolved |
| Mar 17, 2026 | app.circle.so is down## Degraded Performance on March 17th, 2026. **Incident Summary** Between **17:00 UTC and 18:20 UTC**, we experienced a **partial outage and degraded performance** across the platform. During this time, some… | 1h 14m | Resolved |
| Mar 17, 2026 | Degraded performanceThis incident has been resolved. | 1h 9m | Resolved |
| Feb 24, 2026 | app.circle.so is downThis incident has been resolved. | 6 min | Resolved |
| Feb 6, 2026 | app.circle.so is downWe experienced a service disruption lasting approximately 15 minutes due to increased database load. Service has been restored, and our engineering team is actively working on a fix to prevent recurrence. | 0 min | Resolved |
| Feb 5, 2026 | app.circle.so is downThis incident has been resolved. | 3 min | Resolved |
| Feb 3, 2026 | app.circle.so is downThis incident has been resolved. On February 3rd, Circle experienced degraded performance for approximately one minute. | -1 min | Resolved |
| Jan 26, 2026 | app.circle.so is downDue to elevated load on our database, community functionality was down for 25 minutes, followed by 1 hour of degraded performance. The core issue was resolved as of 15:45, and all systems are now operating normally… | 1h 34m | Resolved |
| Jan 20, 2026 | Audience Management Service OutageThis incident has been resolved. | 30 min | Resolved |
| Jan 14, 2026 | app.circle.so is downThis 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. | 39 min | Resolved |
| Jan 14, 2026 | Degraded performance - WorkflowsThis 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. | 1h 2m | Resolved |
| Jan 11, 2026 | Server maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Dec 19, 2025 | app.circle.so is downThis incident has been resolved. On December 19, Circle experienced a brief period (few minutes) of degraded performance and partial unavailability. The issue was caused by a bug in the AI Agents knowledge import… | 3 min | Resolved |
| Dec 17, 2025 | app.circle.so is down**Total duration of related service interruptions:** Approximately 11 minutes **Summary** On December 16, Circle experienced a short period of degraded performance and partial unavailability. The issue was caused by… | 2 min | Resolved |
| Dec 17, 2025 | app.circle.so is downThis incident has been resolved. | 5 min | Resolved |
| Dec 16, 2025 | app.circle.so is downThis incident has been resolved. | 1 min | Resolved |
| Dec 5, 2025 | Degraded performance - [CloudFlare incident]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. | 32 min | Resolved |
| Nov 18, 2025 | Degraded performance - [CloudFlare incident]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. | 1h 59m | Resolved |
| Nov 6, 2025 | Degraded performance: WorkflowsThis incident has been resolved. | 1h 2m | Resolved |
| Nov 5, 2025 | app.circle.so is downThis incident has been resolved. | 6 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Circle incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Circle Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Circle acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Circle outage in this window ran 1d, against a mean recovery of 56 min. If you depend on Circle in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.