Is Circle.so down?

Last checked 8m ago
Current status
Circle.so is up

No incidents right now.

Official status page: https://status.circle.so · Polled every 5 minutes · 17 components tracked

Circle.so is operational right now. Last checked 8m ago; the most recent incident resolved 16d ago.

Real-time Circle.so status, recent outages, and incident history — pulled directly from Circle.so's official status page at https://status.circle.so every 5 minutes. Pingoru tracks 17 Circle.so services and has captured 32 incidents in the last 90 days (99.70% uptime). Get email, Slack, Discord, or webhook alerts the moment Circle.so reports a new incident — free for 5 monitors, no credit card.

Users who monitor Circle.so also follow these Chat services: Discord Anthropic MessageBird Second Life LiveChat Ada Stream Bettermode SAP Conversational AI Landbot View all 6,000+ providers
Circle.so uptime 99.70% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 28m
    Started May 28, 2026, 04:44 PM UTC · Resolved May 28, 2026, 08:12 PM UTC
    Workflows
    Timeline · 5 updates
    • investigating · May 28, 2026, 04:44 PM UTC

      We are currently investigating this issue.

    • identified · May 28, 2026, 05:12 PM UTC

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

    • monitoring · May 28, 2026, 06:46 PM UTC

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

    • 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.

    • 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.

    Latest: ## 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. …

  2. Resolved 2m
    Started May 22, 2026, 01:26 PM UTC · Resolved May 22, 2026, 01:28 PM UTC
    Timeline · 2 updates
    • investigating · May 22, 2026, 01:26 PM UTC

      We are currently investigating this issue.

    • resolved · May 22, 2026, 07:20 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 3m
    Started May 20, 2026, 04:12 PM UTC · Resolved May 20, 2026, 04:15 PM UTC
    Timeline · 2 updates
    • investigating · May 20, 2026, 04:12 PM UTC

      We are currently investigating this issue.

    • resolved · May 20, 2026, 04:15 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 2m
    Started May 09, 2026, 03:12 AM UTC · Resolved May 09, 2026, 03:15 AM UTC
    Timeline · 2 updates
    • investigating · May 09, 2026, 03:12 AM UTC

      We are currently investigating this issue.

    • resolved · May 09, 2026, 03:43 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 1h 42m
    Started Apr 30, 2026, 06:00 PM UTC · Resolved Apr 30, 2026, 07:43 PM UTC
    Timeline · 3 updates
    • investigating · Apr 30, 2026, 06:00 PM UTC

      We are currently investigating this issue.

    • resolved · Apr 30, 2026, 07:43 PM UTC

      This incident has been resolved.

    • 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.

    Latest: 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…

See the full Circle.so outage history

27 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Circle.so outage history →

Or sign up free to get alerts when Circle.so breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 32 incidents View full outage history →