RewindexScorecards
How vendors report incidents
For the 152 vendors with enough history to compare: how often the first post said “resolved”, how long incidents last, how many are major, and which incidents they rewrote or deleted. Built from every archived version of their status pages.
Provisional. Updated nightly, last on Oct 19. Lower is better in every column; select a column to put the highest first.
Typical vendor: 6% posted after it was over, 2 h to resolve, 1.2 major incidents a month.
| Vendor | Posted only after it was over | Time to resolve | Major a month | Rewrites caught |
|---|---|---|---|---|
| Akamaicloud | 12% 6 of 50 | 15 h 19 min | 0.2 | none |
| Amazon Web Servicescloud | 4% 1 of 28 | 2 h 16 min | 0.3 | none |
| Bunny.netcloud | 0% 0 of 50 | 3 h 30 min | 0.7 | none |
| Cloudflarecloud | 27% 14 of 52 | 2 h 2 min | 3.9 | 3 deleted |
| DigitalOceancloud | 10% 5 of 50 | 2 h 48 min | 0.8 | none |
| DNSimplecloud | 0% 0 of 49 | 1 h 42 min | 0.3 | none |
| Linode (Akamai)cloud | 8% 4 of 49 | 5 h 47 min | 0.7 | 1 deleted |
| Scalewaycloud | 10% 5 of 50 | 5 h 40 min | 4.9 | none |
Built nightly from every archived version of each vendor’s status page (rwx_api.vendor_reliability). Comparable vendors have >= 20 incidents in 365 days and >= 10 with full update detail; vendors that share one status page are compared once. Time-to-acknowledge, late-post and backdated rates are left out because they follow each status platform’s start-time convention. Rewrites are counts since 10-minute tracking began on 2026-10-17. Provisional. 174 more vendors are not compared yet.