Two kinds of page live here. A write-up is the measured record of one outage we detected: which of our regions failed first, which recovered last, what people reported and what the vendor's own status page claimed over the same hours, frozen at publication. A reliability report ranks services within a category over a fixed window. The methodology page is the single description of what a reading means. Read as a feed: Atom.
Published
Nothing published yet. The first pieces will be rapid write-ups of outages our probes detect, published within hours of the event with the regional timeline and nothing invented; reliability reports follow once the services they rank have a full quarter of coverage. The schedule below says when.
Reliability by category, last 90 days
Recomputed on each visit from probe-detected outage events only, for services we watched throughout the window. A category shows a ranking only once every service in it has the coverage the claim needs; until then it says so, with the date that changes.
- Measurement window
- 2026-05-25 00:00 UTC to 2026-08-23 00:00 UTC
- Methodology
- version v2-2026-08-22
- Coverage
- Tracking cloud and dev infra services since Aug 20, 2026 (3 days of coverage)
- Figures
- Live, recomputed on each visit
Not enough coverage yet
We have been tracking cloud and dev infra services since Aug 20, 2026. A reliability report and league table needs 90 days of coverage for every service it speaks for, and we are 87 days short; the earliest it could be published is Nov 18, 2026.
We do not publish a ranking, an average or a share from a record shorter than the claim it makes. The measurements keep accumulating in the meantime, and each service's own page shows everything we have measured so far.
- Measurement window
- 2026-05-25 00:00 UTC to 2026-08-23 00:00 UTC
- Methodology
- version v2-2026-08-22
- Coverage
- Tracking social and communication services since Aug 20, 2026 (3 days of coverage)
- Figures
- Live, recomputed on each visit
Not enough coverage yet
We have been tracking social and communication services since Aug 20, 2026. A reliability report and league table needs 90 days of coverage for every service it speaks for, and we are 87 days short; the earliest it could be published is Nov 18, 2026.
We do not publish a ranking, an average or a share from a record shorter than the claim it makes. The measurements keep accumulating in the meantime, and each service's own page shows everything we have measured so far.
- Measurement window
- 2026-05-25 00:00 UTC to 2026-08-23 00:00 UTC
- Methodology
- version v2-2026-08-22
- Coverage
- Tracking payments services since Aug 20, 2026 (3 days of coverage)
- Figures
- Live, recomputed on each visit
Not enough coverage yet
We have been tracking payments services since Aug 20, 2026. A reliability report and league table needs 90 days of coverage for every service it speaks for, and we are 87 days short; the earliest it could be published is Nov 18, 2026.
We do not publish a ranking, an average or a share from a record shorter than the claim it makes. The measurements keep accumulating in the meantime, and each service's own page shows everything we have measured so far.
- Measurement window
- 2026-05-25 00:00 UTC to 2026-08-23 00:00 UTC
- Methodology
- version v2-2026-08-22
- Coverage
- Tracking gaming services since Aug 20, 2026 (3 days of coverage)
- Figures
- Live, recomputed on each visit
Not enough coverage yet
We have been tracking gaming services since Aug 20, 2026. A reliability report and league table needs 90 days of coverage for every service it speaks for, and we are 87 days short; the earliest it could be published is Nov 18, 2026.
We do not publish a ranking, an average or a share from a record shorter than the claim it makes. The measurements keep accumulating in the meantime, and each service's own page shows everything we have measured so far.
- Measurement window
- 2026-05-25 00:00 UTC to 2026-08-23 00:00 UTC
- Methodology
- version v2-2026-08-22
- Coverage
- Tracking consumer services since Aug 20, 2026 (3 days of coverage)
- Figures
- Live, recomputed on each visit
Not enough coverage yet
We have been tracking consumer services since Aug 20, 2026. A reliability report and league table needs 90 days of coverage for every service it speaks for, and we are 87 days short; the earliest it could be published is Nov 18, 2026.
We do not publish a ranking, an average or a share from a record shorter than the claim it makes. The measurements keep accumulating in the meantime, and each service's own page shows everything we have measured so far.
- Measurement window
- 2026-05-25 00:00 UTC to 2026-08-23 00:00 UTC
- Methodology
- version v2-2026-08-22
- Coverage
- Tracking other services since Aug 20, 2026 (3 days of coverage)
- Figures
- Live, recomputed on each visit
Not enough coverage yet
We have been tracking other services since Aug 20, 2026. A reliability report and league table needs 90 days of coverage for every service it speaks for, and we are 87 days short; the earliest it could be published is Nov 18, 2026.
We do not publish a ranking, an average or a share from a record shorter than the claim it makes. The measurements keep accumulating in the meantime, and each service's own page shows everything we have measured so far.
What we publish, and when
Claims scale with coverage age. Each kind of piece has a coverage bar every service it speaks for must clear, and a sample floor. The dates below are computed from when our record actually began (the oldest service has been tracked since Aug 20, 2026, 3 days); a ranking of younger services unlocks later, per its youngest member. Methodology in force: version v2-2026-08-22.
| Kind of piece | Coverage needed | Sample floor | Earliest, from the oldest record | Today |
|---|---|---|---|---|
| Rapid incident write-up | from day one | 1 event | Aug 20, 2026 | allowed |
| Regional latency baseline (internet weather) | 30 days | 3 services | Sep 19, 2026 | not yet (27 days short) |
| Reliability report and league table | 90 days | 3 services | Nov 18, 2026 | not yet (87 days short) |
| Single-region outage share | 180 days | 25 events | Feb 16, 2027 | not yet (177 days short) |
| Crowd reports versus probes | 180 days | 25 events | Feb 16, 2027 | not yet (177 days short) |
| SLA and latency geography | 365 days | 3 services | Aug 20, 2027 | not yet (362 days short) |
The sample floor counts only what has a full record over the window; a service added part-way through is left out of a ranking, by name, rather than ranked on part of it.