← Back to Incident History
Resend Reliability
Transactional email delivery for applications
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 16 of 25 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% weightProvider-reported incident duration97
Total incident hours: 73.2
An uptime proxy, not measured availability. Overlapping incidents are added together, including across products and regions.
🚀Resolution Speed
25% weightHow fast issues are resolved84
Avg fix time: 4h 35m
16 of 16 included incidents have measured fix times.
📊Incident Frequency
20% weightLower is better77
Included incidents in period: 16
Severity-weighted incident count. Providers cover different numbers of products and regions, so comparisons are approximate.
💬Communication
20% weightUpdates, ack time, workarounds83
Avg updates per incident: 3.3
16 of 16 included incidents have update counts; 16 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%.