← Back to Incident History
83B
GoodProvisional

Score Summary

  • Geographic scopeProvider-wide
  • PeriodLast 90 days
  • Recorded incidents in period7
  • Incidents included in score6
  • Categorycloud
  • Importancecritical

Data notes · Provisional score

  • Some incidents have incomplete timing evidence.
  • Some incident lifecycle states lack matching resolution evidence.
  • Some resolved incidents have missing or inconsistent fix-time measurements.
  • Some incidents have missing or invalid communication measurements.

The score uses 6 of 7 recorded incidents with usable timing. Incomplete or conflicting intervals are excluded from the calculation and remain in incident history. These notes are reassessed as the underlying records are repaired.

Score Breakdown

⏱️Uptime
35% weight
Provider-reported incident duration96
Total incident hours: 82.8

An uptime proxy, not measured availability. Overlapping incidents are added together, including across products and regions.

🚀Resolution Speed
25% weight
How fast issues are resolved44
Avg fix time: 13h 48m

6 of 6 included incidents have measured fix times.

📊Incident Frequency
20% weight
Lower is better94
Included incidents in period: 6

Severity-weighted incident count. Providers cover different numbers of products and regions, so comparisons are approximate.

💬Communication
20% weight
Updates, ack time, workarounds97
Avg updates per incident: 6.3

6 of 6 included incidents have update counts; 6 have acknowledgement times.

Scores describe collected provider-reported incidents, not independently measured uptime or complete historical coverage. The formula weights are unchanged: uptime proxy 35%, resolution speed 25%, incident frequency 20%, and communication 20%.