Circle.so Outage History

Circle.so is up right now

Circle.so had 11 outages in the last 2 years totaling 18h 18m of downtime — averaging 0.5 incidents per month.

There were 11 Circle.so outages since August 29, 2025 totaling 18h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.circle.so

Notice May 22, 2026

app.circle.so is down

Detected by Pingoru
May 22, 2026, 01:26 PM UTC
Resolved
May 22, 2026, 01:28 PM UTC
Duration
2m
Timeline · 2 updates
  1. investigating May 22, 2026, 01:26 PM UTC

    We are currently investigating this issue.

  2. resolved May 22, 2026, 07:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 15, 2026

Mobile API endpoint errors

Detected by Pingoru
Apr 15, 2026, 08:16 PM UTC
Resolved
Apr 09, 2026, 03:57 PM UTC
Duration
Timeline · 2 updates
  1. resolved Apr 15, 2026, 08:16 PM UTC

    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.

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

    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.

Read the full incident report →

Minor April 14, 2026

Elasticsearch Degradation

Detected by Pingoru
Apr 14, 2026, 11:50 AM UTC
Resolved
Apr 14, 2026, 11:50 AM UTC
Duration
Timeline · 2 updates
  1. resolved 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.

  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 →

Notice March 17, 2026

Degraded performance

Detected by Pingoru
Mar 17, 2026, 03:45 PM UTC
Resolved
Mar 17, 2026, 04:55 PM UTC
Duration
1h 9m
Timeline · 2 updates
  1. monitoring Mar 17, 2026, 04:45 PM UTC

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

  2. resolved Mar 17, 2026, 04:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 20, 2026

Audience Management Service Outage

Detected by Pingoru
Jan 20, 2026, 10:19 PM UTC
Resolved
Jan 20, 2026, 10:50 PM UTC
Duration
30m
Affected: Sign-up & LoginREST APICircle iOS AppPosts & CommentsCircle Android AppNotificationsBranded AppsDirect Messaging & ChatPaywalls & Member BillingCircle DiscoverLive Streams & RoomsCircle Help CenterCoursesEventsMarketing HubWorkflowsAnalytics
Timeline · 2 updates
  1. investigating Jan 20, 2026, 10:19 PM UTC

    We are currently investigating this issue, which is impacting member visibility and the ability to manage your audience.

  2. resolved Jan 20, 2026, 10:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 14, 2026

Degraded performance - Workflows

Detected by Pingoru
Jan 14, 2026, 06:03 PM UTC
Resolved
Jan 14, 2026, 07:06 PM UTC
Duration
1h 2m
Affected: Workflows
Timeline · 3 updates
  1. investigating Jan 14, 2026, 06:03 PM UTC

    We are currently investigating this issue.

  2. identified Jan 14, 2026, 06:19 PM UTC

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

  3. resolved Jan 14, 2026, 07:06 PM UTC

    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.

Read the full incident report →

Critical December 5, 2025

Degraded performance - [CloudFlare incident]

Detected by Pingoru
Dec 05, 2025, 08:49 AM UTC
Resolved
Dec 05, 2025, 09:21 AM UTC
Duration
32m
Affected: Sign-up & LoginPosts & CommentsNotificationsDirect Messaging & ChatPaywalls & Member BillingCircle DiscoverLive Streams & RoomsCircle Help CenterCoursesEventsMarketing HubWorkflowsAnalytics
Timeline · 3 updates
  1. investigating Dec 05, 2025, 08:49 AM UTC

    We are currently investigating this issue.

  2. resolved Dec 05, 2025, 09:21 AM UTC

    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.

  3. postmortem Dec 05, 2025, 09:27 AM UTC

    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.

Read the full incident report →

Minor November 6, 2025

Degraded performance: Workflows

Detected by Pingoru
Nov 06, 2025, 06:09 PM UTC
Resolved
Nov 06, 2025, 07:12 PM UTC
Duration
1h 2m
Affected: Marketing HubWorkflows
Timeline · 2 updates
  1. investigating Nov 06, 2025, 06:30 PM UTC

    An issue with workflow execution has been identified, and a fix is being implemented.

  2. resolved Nov 06, 2025, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 21, 2025

Degraded performance: Android app

Detected by Pingoru
Oct 21, 2025, 01:55 PM UTC
Resolved
Oct 21, 2025, 06:53 PM UTC
Duration
4h 57m
Affected: Circle Android App
Timeline · 3 updates
  1. investigating Oct 21, 2025, 01:55 PM UTC

    We are experiencing instability on a small percentage of Android devices and are currently investigating the issue.

  2. resolved Oct 21, 2025, 06:53 PM UTC

    This incident has been resolved.

  3. postmortem Oct 21, 2025, 06:59 PM UTC

    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.

Read the full incident report →

Minor October 20, 2025

Degraded performance: Analytics, notifications, mobile apps

Detected by Pingoru
Oct 20, 2025, 04:29 PM UTC
Resolved
Oct 20, 2025, 10:02 PM UTC
Duration
5h 32m
Affected: Circle Android AppNotificationsBranded AppsAnalytics
Timeline · 3 updates
  1. identified Oct 20, 2025, 04:29 PM UTC

    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

  2. monitoring Oct 20, 2025, 07:55 PM UTC

    In-app notifications and analytics features are now fully operational. We will continue to monitor closely to ensure stability.

  3. resolved Oct 20, 2025, 10:02 PM UTC

    AWS has resolved the incident. All systems are operating normally. We’ll continue to monitor for stability.

Read the full incident report →