Partial outage (degraded check response and elevated 500 errors)

What to do

• Check whether your product depends on Autumn. 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-10-30 08:24 UTC and 2026-10-30 00:50 UTC may need a replay.

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

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

Updates from Autumn 2

1. identifiedOct 30, 2026, 12:46 AM UTC

   The issue has been identified and we are working on resolving it.

   provider

2. resolvedOct 30, 2026, 12:50 AM UTC

   The issue has now been fully resolved. Incident summary: Oct 30, 2026, 00:44–00:52 UTC. A burst of unusually expensive bulk operations on one API endpoint (entities.delete) overloaded our primary database. API requests that needed the database slowed down or timed out. Some endpoints returned 500, 503 or 504 errors, mostly between 00:44 and 00:47 UTC. Balance checks failed open. At the peak, around 00:47 UTC, up to 40% of check calls returned our fail-open response instead of a live balance: HTTP 202 with allowed: true and balance: null. No events were lost and all balances caught up. We’ve since added stricter rate limits to the endpoint involved and an index to optimize its queries.

   provider

Corrections

None so far.

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