Incident Library

Component

Database proxy and connection pooler

데이터베이스 프록시와 커넥션 풀러 · database-proxy

13 cases · 2022 to 2026

Root cause Breaking change in an upgrade4Faulty deployment3Capacity exhaustion2Configuration change2Cloud provider outage1Software defect1
Contributing factor Unrepresentative staging4Unverified assumption3Automation amplification3Monitoring blind spot3Retry storm3Unpinned version3Excessive blast radius2Harmful manual action2No staged rollout2Overlapping failures2Change during peak hours1Unreviewed defaults1Inefficient query1Unknown limit1Limited debug access1No configuration tests1Health check tied to a dependency1
Symptom Service outage7Database overload6High error rate4High latency4Connection pool exhaustion3Intermittent timeouts2Lock contention or deadlock2Scale-up failure1Connection resets1Deploys failing1DNS resolution failures1Failover failure1Intermittent connection failures1Network unreachable1Probe failures1Replication lag1Writes rejected1
Organisation Railway3Clerk1Decagon1Discord1Gadget1GitHub1Intercom1PlanetScale1RevenueCat1Safie1Supabase1

Cases, by severity

  1. IL-0574 Aurora MySQL writer CPU stuck near 100% minutes after Safie pointed production at a new Amazon RDS ProxySafie · 2026

    Root cause Configuration change

  2. IL-0313 Decagon voice requests stalled for exactly 300 seconds behind self-managed PgBouncer and exhausted the SQLAlchemy poolDecagon · 2026

    Root cause Software defect

  3. IL-0499 Discord voice and video calls hung at Awaiting Endpoint for three hours after 17% of sessions stopped at onceDiscord · 2026

    Root cause Configuration change

  4. IL-0304 Intercom's US region was fully down for 71 minutes when its Vitess VTGates dropped all routes to the database shardsIntercom · 2026

    Root cause Breaking change in an upgrade

  5. IL-0369 Railway's backend API went down when a column migration waited on locks and replicas could not get database connectionsRailway · 2025

    Root cause Faulty deployment

  6. IL-0315 Railway's backend API went down when an index build locked a billion-row Postgres table and used up every connectionRailway · 2025

    Root cause Faulty deployment

  7. IL-0368 PlanetScale's control plane went down and some database branches failed queries during the AWS us-east-1 outagePlanetScale · 2025

    Root cause Cloud provider outage

  8. IL-0316 Railway's control plane slowed and deployments stopped after a PgBouncer version jump used abnormal CPU and memoryRailway · 2025

    Root cause Breaking change in an upgrade

  9. IL-0498 Clerk's Postgres database had load spikes every 15 minutes and requests failed and slowed intermittently for four daysClerk · 2025

    Root cause Breaking change in an upgrade

  10. IL-0307 Supabase's Postgres connection pooler Supavisor 2.0 dropped connections for about 80% of us-east-1 tenantsSupabase · 2025

    Root cause Faulty deployment

  11. IL-0312 Gadget's main Postgres did not start again after a restart to raise max_connections, and the platform went downGadget · 2024

    Root cause Capacity exhaustion

  12. IL-0308 Most RevenueCat backend systems failed after cutover to a new Aurora PostgreSQL 14 cluster as queries became very slowRevenueCat · 2022

    Root cause Breaking change in an upgrade

  13. IL-0302 Peak load on GitHub's mysql1 MySQL cluster maxed out its database proxy's connections and stopped writes in March 2022GitHub · 2022

    Root cause Capacity exhaustion

View on the graph