← Back to Incident History
67D
Poor

Score Summary

  • Geographic scopeProvider-wide
  • PeriodLast 90 days
  • Recorded incidents in period3
  • Incidents included in score3
  • Categorydevtools
  • Importancehigh

Score Breakdown

⏱️Uptime
35% weight
Provider-reported incident duration89
Total incident hours: 239.9

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

🚀Resolution Speed
25% weight
How fast issues are resolved0
Avg fix time: 3d 7h

3 of 3 included incidents have measured fix times.

📊Incident Frequency
20% weight
Lower is better91
Included incidents in period: 3

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

💬Communication
20% weight
Updates, ack time, workarounds87
Avg updates per incident: 4.7

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