Postmortem: Delayed Start Compute Operations

The Neon team experienced two significant outages on May 16 and May 19, 2025, in the AWS us-east-1 region, affecting customers' ability to create or start inactive databases. The root cause of these incidents was related to IP address allocation issues due to a high number of active pods exhausting available IP addresses in subnets. To mitigate this, the team made changes to their Kubernetes architecture and AWS CNI configuration, including doubling the size of prewarmed compute pools and increasing VPC subnet sizes. These measures prevented future IP allocation errors, but further investigation is ongoing to understand the root causes of these incidents.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.