# Partial outage (degraded check response and elevated 500 errors)

- Provider: [Autumn](https://down.guide/autumn)
- Level: confirmed
- Impact: Partial outage
- lasted 0m
- started 2026-10-30 08:24 UTC
- id: DWN-90a329d436
- Official page: https://status.useautumn.com/incidents/01M65YHDDF07Z89VZYMABZ42W6

## Updates from Autumn
### 2026-10-30 00:46 UTC: identified
The issue has been identified and we are working on resolving it.

### 2026-10-30 00:50 UTC: resolved
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.

From the builder: does your app depend on Autumn? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=autumn) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Autumn.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-90a329d436), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.