Mobile API endpoint errors

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 0m it lasted.

  Anything that failed between 2026-04-15 20:16 UTC and 2026-04-09 15:57 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 2

1. resolvedApr 9, 2026, 3:57 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.

   provider

2. postmortemApr 15, 2026, 8: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.

   provider

Corrections

None so far.

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