Inngest outage: service restarts depended on the database that went down

Inngest suffered two disruption windows on October 20, 2026, from 13:00 to 13:15 and 15:20 to 15:35 UTC, caused by lost connectivity between its infrastructure and database. Event ingestion services restarted after memory exhaustion but could not finish booting without the same database, extending the outage.

• Two outage windows on October 20: 13:00–13:15 and 15:20–15:35 UTC
• Event ingestion, scheduling and execution were down or slowed
• Restarts required a connection to the same database that failed
• Inngest did not name the root cause of the database connectivity loss