app.circle.so is down

What to do

• Check whether your product depends on Circle. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 15m it lasted.

  Anything that failed between 2026-03-17 17:07 UTC and 2026-03-17 18:21 UTC may need a replay.

• Subscribe to Circle's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=circle works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Circle 3

1. investigatingMar 17, 2026, 5:07 PM UTC

   We are currently investigating this issue.

   provider

2. resolvedMar 17, 2026, 6:21 PM UTC

   This incident has been resolved.

   provider

3. postmortemMar 17, 2026, 8:42 PM UTC

   ## 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 actions may have been slow to load or temporarily unresponsive. ‌ **Root Cause** The issue was caused by a disruption in one of our supporting database services. This led to some requests taking longer than expected, which impacted overall application performance. ‌ **Resolution** We restored the affected service, and performance returned to normal shortly after. ‌ **Prevention & Next Steps** We’re taking the following steps to reduce the likelihood of this happening again: * Improving the reliability and monitoring of the affected service * Adding safeguards so the platform continues to operate smoothly even if a supporting service becomes unavailable ‌ We appreciate your patience while we worked to resolve this and apologize for the disruption.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.