Circle.so Outage History

Circle.so is up right now

Pingoru has recorded 57 incidents for Circle.so: 53 in the last 12 months and 7 in the last 90 days.

Source: status.circle.so

57incidents recorded
53last 12 months
7last 90 days
67 minutestypical duration
Incidents per month
02040AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Circle.so in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026221 of 720 (0%)
May 202644 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202640 of 744 (0%)
September 202610 of 720 (0%)
October 202620 of 744 (0%)
November 202600 of 44 (0%)

Incidents, newest first

Notice October 5, 2026 app.circle.so is down 13m Sign-up & Login, Posts & Comments, Notifications, Direct Messaging & Chat and 7 more

Started Oct 05, 2026, 09:44 AM UTC· resolved Oct 05, 2026, 09:57 AM UTC

  1. investigating Oct 05, 2026, 09:44 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 05, 2026, 09:57 AM UTC

    This incident has been resolved. The incident was caused by a missing configuration in the application we use to deploy code changes to the Circle application. After investigating, we immediately applied a temporary patch to restore availability. We then identified the root cause and implemented a permanent fix. All services are operating normally.

  3. postmortem Oct 05, 2026, 03:46 PM UTC

    #### 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 application we use to deploy new code changes to the Circle application #### Mitigation and immediate fixes Upon investigating the issue, we immediately patched this application with a temporary change that restored application availability. Later today, we identified the root cause and applied a definitive fix. #### Status All services are currently operating normally.

Read the full incident report →

Notice October 3, 2026 app.circle.so is down 4m

Started Oct 03, 2026, 08:13 AM UTC· resolved Oct 03, 2026, 08:18 AM UTC

  1. investigating Oct 03, 2026, 08:13 AM UTC

    We are currently investigating this issue.

  2. resolved Oct 03, 2026, 08:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 1, 2026 app.circle.so is down 51m

Started Sep 01, 2026, 01:59 PM UTC· resolved Sep 01, 2026, 02:50 PM UTC

  1. investigating Sep 01, 2026, 01:59 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 01, 2026, 02:50 PM UTC

    Earlier 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. We apologize for any inconvenience.

Read the full incident report →

Notice August 27, 2026 app.circle.so is down 1m Sign-up & Login, REST API, Circle iOS App, Posts & Comments and 13 more

Started Aug 27, 2026, 10:25 PM UTC· resolved Aug 27, 2026, 10:26 PM UTC

  1. investigating Aug 27, 2026, 10:25 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 27, 2026, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 20, 2026 app.circle.so is down 27s

Started Aug 20, 2026, 05:51 PM UTC· resolved Aug 20, 2026, 05:52 PM UTC

  1. investigating Aug 20, 2026, 05:51 PM UTC

    We are currently investigating this issue.

  2. resolved Aug 20, 2026, 05:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 20, 2026 app.circle.so is down 26m

Started Aug 20, 2026, 01:04 PM UTC· resolved Aug 20, 2026, 01:31 PM UTC

  1. investigating Aug 20, 2026, 01:04 PM UTC

    We are currently investigating this issue.

Read the full incident report →

Notice August 19, 2026 app.circle.so is down 16m

Started Aug 19, 2026, 08:52 AM UTC· resolved Aug 19, 2026, 09:08 AM UTC

  1. investigating Aug 19, 2026, 08:52 AM UTC

    We are currently investigating this issue.

  2. resolved Aug 19, 2026, 09:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 28, 2026 Workflows stuck in "In progress" status 3h 28m Workflows

Started May 28, 2026, 04:44 PM UTC· resolved May 28, 2026, 08:12 PM UTC

  1. investigating May 28, 2026, 04:44 PM UTC

    We are currently investigating this issue.

  2. identified May 28, 2026, 05:12 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 28, 2026, 06:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 28, 2026, 08:12 PM UTC

    The issue has been fully resolved and all systems are operating normally. A detailed post-mortem report will be published here shortly. Thank you for your patience and cooperation.

  5. postmortem Jun 01, 2026, 03:06 PM UTC

    ## 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** – The issue began, causing delays in newly scheduled automated workflows. * **15:51** – Our engineering team identified the root cause of the scheduling interruption. * **16:42** – A fix was deployed, restoring normal operations to the background processing framework. * **18:45** – The resulting backlog of delayed tasks was completely cleared and normal service was confirmed. **Root Cause** A routine system update included a software dependency upgrade that unexpectedly conflicted with our background processing framework. This conflict prevented scheduled background jobs from moving into the active processing queue. As a result, automated workflows and other asynchronous actions were delayed, though no underlying data was lost or corrupted during this time. **Resolution** Upon investigating the anomaly in the scheduling queue, our engineering team determined that the recent dependency upgrade was responsible. We immediately reverted the update, which restored the flow of scheduled tasks. To resolve the issue as swiftly as possible, we temporarily scaled up our infrastructure's processing capacity to rapidly clear the backlog of delayed actions. **Preventative Measures** To prevent this type of issue from occurring in the future, we are planning on implementing the following improvements: * **Enhanced Alerting:** We are deploying strict, automated alerts specifically designed to detect anomalies in scheduled task queues, drastically reducing our time to detection. * **Upgraded Telemetry:** We are adding granular, time-series visualizations to our monitoring systems to better track the exact states of background jobs \(scheduled, enqueued, and processed\) in real time. We sincerely apologize for any disruption this may have caused to your operations. The issue was fully mitigated, and all backlogged tasks have been successfully processed.

Read the full incident report →

Notice May 22, 2026 app.circle.so is down 2m

Started May 22, 2026, 01:26 PM UTC· resolved May 22, 2026, 01:28 PM UTC

  1. investigating May 22, 2026, 01:26 PM UTC

    We are currently investigating this issue.

  2. resolved May 22, 2026, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026 app.circle.so is down 1m

Started May 20, 2026, 04:12 PM UTC· resolved May 20, 2026, 04:13 PM UTC

  1. investigating May 20, 2026, 04:12 PM UTC

    We are currently investigating this issue.

  2. resolved May 20, 2026, 04:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 9, 2026 app.circle.so is down 52s

Started May 09, 2026, 03:12 AM UTC· resolved May 09, 2026, 03:13 AM UTC

  1. investigating May 09, 2026, 03:12 AM UTC

    We are currently investigating this issue.

  2. resolved May 09, 2026, 03:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 30, 2026 app.circle.so is down 1h 42m

Started Apr 30, 2026, 06:00 PM UTC· resolved Apr 30, 2026, 07:43 PM UTC

  1. investigating Apr 30, 2026, 06:00 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 30, 2026, 07:43 PM UTC

    This incident has been resolved.

  3. postmortem Apr 30, 2026, 07:43 PM UTC

    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.

Read the full incident report →

Notice April 30, 2026 app.circle.so is down 11m

Started Apr 30, 2026, 02:35 PM UTC· resolved Apr 30, 2026, 02:46 PM UTC

  1. investigating Apr 30, 2026, 02:35 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 30, 2026, 02:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 30, 2026 app.circle.so is down 3m

Started Apr 30, 2026, 11:36 AM UTC· resolved Apr 30, 2026, 11:39 AM UTC

  1. investigating Apr 30, 2026, 11:36 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 30, 2026, 11:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 30, 2026 app.circle.so is down 1m

Started Apr 30, 2026, 10:45 AM UTC· resolved Apr 30, 2026, 10:47 AM UTC

  1. investigating Apr 30, 2026, 10:45 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 30, 2026, 10:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 19, 2026 app.circle.so is down 1h 41m

Started Apr 19, 2026, 04:50 PM UTC· resolved Apr 19, 2026, 06:32 PM UTC

  1. investigating Apr 19, 2026, 04:50 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 19, 2026, 06:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 19, 2026 app.circle.so is down 13m

Started Apr 19, 2026, 01:01 AM UTC· resolved Apr 19, 2026, 01:15 AM UTC

  1. investigating Apr 19, 2026, 01:01 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 19, 2026, 01:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 17, 2026 app.circle.so is down 1m Sign-up & Login, REST API, Circle iOS App, Posts & Comments and 13 more

Started Apr 17, 2026, 06:53 PM UTC· resolved Apr 17, 2026, 06:54 PM UTC

  1. investigating Apr 17, 2026, 06:53 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 17, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 14, 2026 Elasticsearch Degradation –

Started Apr 14, 2026, 11:50 AM UTC· resolved Apr 14, 2026, 11:50 AM UTC

  1. resolved Apr 14, 2026, 11:50 AM UTC

    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.

  2. postmortem Apr 15, 2026, 08:01 PM UTC

    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.

Read the full incident report →

Minor April 14, 2026 app.circle.so is down 3m

Started Apr 14, 2026, 04:17 AM UTC· resolved Apr 14, 2026, 04:21 AM UTC

  1. investigating Apr 14, 2026, 04:17 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 14, 2026, 04:21 AM UTC

    This incident has been resolved.

  3. postmortem Apr 15, 2026, 07:50 PM UTC

    Communities 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 escalation to AWS \(case 177616832700336\), and both cases have been escalated to AWS's highest priority tier. We are actively working with AWS to resolve the underlying infrastructure issue and have additional safeguards in place.

Read the full incident report →

Minor April 14, 2026 app.circle.so is down 26m

Started Apr 14, 2026, 01:50 AM UTC· resolved Apr 14, 2026, 02:17 AM UTC

  1. investigating Apr 14, 2026, 01:50 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 14, 2026, 02:17 AM UTC

    This incident has been resolved.

  3. postmortem Apr 15, 2026, 08:05 PM UTC

    Communities 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 different availability zone to restore service. The crash was caused by an AWS RDS bug that we had already escalated to AWS support. We are working with AWS to prevent recurrence and have additional monitoring in place to detect database instability earlier.

Read the full incident report →

Notice April 13, 2026 app.circle.so is down 5m Sign-up & Login, REST API, Circle iOS App, Posts & Comments and 13 more

Started Apr 13, 2026, 09:14 PM UTC· resolved Apr 13, 2026, 09:20 PM UTC

  1. investigating Apr 13, 2026, 09:14 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 13, 2026, 09:20 PM UTC

    This incident has been resolved.

  3. postmortem Apr 15, 2026, 08:10 PM UTC

    Communities 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 after and resolved both issues.

Read the full incident report →

Notice April 13, 2026 app.circle.so is down 3m Sign-up & Login, REST API, Circle iOS App, Posts & Comments and 13 more

Started Apr 13, 2026, 08:21 PM UTC· resolved Apr 13, 2026, 08:24 PM UTC

  1. investigating Apr 13, 2026, 08:21 PM UTC

    We are currently investigating this issue.

  2. resolved Apr 13, 2026, 08:24 PM UTC

    This incident has been resolved.

  3. postmortem Apr 15, 2026, 08:09 PM UTC

    Communities 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 database. Our team identified the specific query and deployed a fix the same day to reduce query frequency.

Read the full incident report →

Notice April 10, 2026 app.circle.so is down 2m

Started Apr 10, 2026, 10:40 AM UTC· resolved Apr 10, 2026, 10:42 AM UTC

  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.

Read the full incident report →

Notice April 9, 2026 app.circle.so is down 2m

Started Apr 09, 2026, 11:21 AM UTC· resolved Apr 09, 2026, 11:23 AM UTC

  1. investigating Apr 09, 2026, 11:21 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 09, 2026, 11:23 AM UTC

    This incident has been resolved.

  3. postmortem Apr 15, 2026, 08:13 PM UTC

    Brief 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 deployed.

Read the full incident report →