| Cause | Incidents | Major | Median time | By month | Most affected |
|---|
| Capacity and loadTraffic, resource exhaustion or scaling limits overwhelmed the system. | 111 | 33 | 1h 29m |
|     |
| Third-party dependencyAn upstream provider or another service the product relies on failed. | 104 | 41 | 2h 8m |
|     |
| Configuration changeA setting, policy, feature flag or config file pushed to production broke something. | 103 | 42 | 56m |
|     |
| NetworkRouting, BGP, backbone, load balancer or connectivity faults. | 86 | 32 | 1h 33m |
|     |
| DatabaseA database failover, overload, corruption or replication fault. | 58 | 22 | 1h 1m |
|     |
| Deployment or rolloutA code release, migration or rollout that had to be rolled back. | 37 | 18 | 1h 22m |
|     |
| StorageObject, block or file storage became slow or unavailable. | 28 | 11 | 6h 18m |
|     |
| Software bugA latent defect in the vendor’s own software surfaced. | 22 | 7 | 1h 4m |
|     |
| DNSName resolution failed or returned the wrong answer. | 17 | 9 | 1h 18m |
|     |
| Power and facilitiesPower, cooling, fire or a data center facility problem. | 9 | 8 | 15h 42m |
|     |
| Certificate or TLSAn expired, revoked or misissued certificate. | 6 | 4 | 1h 19m |
|    |