Down Index methodology
Every confirmed incident is scored from its own facts. Maintenance, narrow-scope incidents (one country, region, site, carrier or asset) and imported history are never scored. Weekly tables freeze when the ISO week ends (UTC).
Five parts, 100 points
Impact (30 points)
The worst impact the provider posted: major outage 30, partial outage 18, degraded 8.
Breadth (20 points)
The share of the provider's components affected, or the number of regions (five or more is full marks).
Duration (15 points)
Log-scaled minutes from start to resolution; 12 hours is full marks.
Reach (20 points)
How many builds depend on the provider: weekly registry downloads of its official SDKs plus the catalog providers that run on it, relative to the most-depended-on provider.
Acknowledgement (15 points)
Minutes between down.guide's first corroborated evidence and the provider's first post; 60 minutes is full marks.