Neon experienced significant stability issues in May and June 2025 due to unexpected 5x increase in database creation and 50x increase in branch creation driven by agentic AI platforms. May incidents were caused by hitting Kubernetes scaling limits before their horizontal scaling solution (Cells) was ready. June problems stemmed from control plane database scaling issues under massive branch creation load. The company has implemented Cells architecture, improved rate limiting, updated testing scenarios, and plans to isolate database management into a separate service to prevent future incidents.
Table of contents
May: Capacity Handling and “Cells”June: Metadata HandlingUp Next: Better Component IsolationHow Bad Was It?Where to go from hereSort: