Quarter by quarter, since 2025
The same 258 vendors in every quarter: those whose full incident history we hold since January 2025. Rates are incidents per month, which keeps the quarter in progress comparable. The median vendor is the typical one: a few vendors post over 100 incidents a month and pull the average up, so look at the median first.
| Quarter | Incidents per month, median vendor | Average | Busiest vendor | Median to resolution | Major or critical |
|---|---|---|---|---|---|
| Q1 2025 | 2.4 | 5.7 | Twilio 163 a month | 1h 12m | 20% |
| Q2 2025 | 2.7 | 5.4 | Twilio 160 a month | 1h 46m | 26% |
| Q3 2025 | 2.6 | 5.7 | Twilio 175 a month | 1h 44m | 25% |
| Q4 2025 | 3.0 | 5.8 | Twilio 182 a month | 1h 59m | 30% |
| Q1 2026 | 2.7 | 6.4 | Twilio 161 a month | 1h 34m | 24% |
| Q2 2026 | 3.0 | 6.2 | Twilio 140 a month | 1h 36m | 25% |
| Q3 2026 | 2.3 | 6.2 | Twilio 184 a month | 1h 32m | 26% |
| Q4 2026 so far | 3.0 | 7.0 | Palo Alto Networks 182 a month | 1h 44m | 27% |
Read this with care
Quarters before collection started come from vendors' history pages, which give each incident's time range, impact and final update, but not every update. That is enough for counts, durations and impact, but not for time to mitigation or for comparing what failed, so those stay in the quarterly reports. Vendors whose pages only show recent incidents, such as those on incident.io, AWS and Google Cloud, are left out until their recorded history covers the whole period. Counts measure how much vendors post as much as how often they fail.