← Back to Incident History
92A
Very GoodProvisional

Score Summary

  • Geographic scopeProvider-wide
  • PeriodLast 90 days
  • Recorded incidents in period14
  • Incidents included in score12
  • Categorydevtools
  • Importancehigh

Data notes · Provisional score

  • Some incidents have incomplete timing evidence.
  • Some incident timestamps are invalid or outside the reporting window.
  • Some resolved incidents have missing or inconsistent fix-time measurements.
  • Some incidents have missing or invalid communication measurements.

The score uses 12 of 14 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 duration100
Total incident hours: 6.3

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

🚀Resolution Speed
25% weight
How fast issues are resolved100
Avg fix time: 31m

12 of 12 included incidents have measured fix times.

📊Incident Frequency
20% weight
Lower is better81
Included incidents in period: 12

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

💬Communication
20% weight
Updates, ack time, workarounds78
Avg updates per incident: 2.8

12 of 12 included incidents have update counts; 12 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%.