Inefficient query

Cases

1. IL-0510 MIT Learn's RDS PostgreSQL ran out of storage after a release and learn.mit.edu returned 503s and 504s for hoursMIT Open Learning · 2026

   Root cause Faulty deployment

2. IL-0317 Clerk's Postgres slowed after an automatic analyze flipped a query plan, and over 95% of requests got 429Clerk · 2026

   Root cause Query plan regression

3. IL-0287 One overloaded shard of MongoDB's internal monitoring database delayed Atlas metrics, alerts and cluster operationsMongoDB · 2025

   Root cause Capacity exhaustion

4. IL-0551 Bitbucket Cloud's overloaded primary database failed over, and the website, API and Pipelines were slow for almost a dayAtlassian · 2025

   Root cause Capacity exhaustion

5. IL-0571 STORES reservation returned bursts of 504 errors when a smart-list query held a database process for over 20 minutesSTORES · 2024

   Root cause Faulty deployment

6. IL-0447 An every RDS for MySQL instance slowed badly when its gp2 EBS BurstBalance ran out and IOPS fell to the baselineevery · 2024

   Root cause Capacity exhaustion

7. IL-0567 Aurora MySQL behind Cookie Run: OvenBreak hit 100% CPU after a sales-ranking feature launch, and players could not playDevsisters · 2023

   Root cause Faulty deployment

8. IL-0326 A retention clean-up job filled the disk of MailPace's managed Postgres, which stayed offline for just over two hoursMailPace · 2023

   Root cause Capacity exhaustion

9. 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

10. IL-0212 Many Slack users could not connect because a Vitess keyspace for channel membership was overloaded by cache-miss queriesSlack · 2022

    Root cause Capacity exhaustion

11. IL-0456 Inflearn went down six times during a January 2022 free-course event as slow queries piled up on Aurora PostgreSQLInflab · 2022

    Root cause Capacity exhaustion