Resend: SLA evidence report
Resend: SLA evidence report
We hold no probe record for Resend: we read its status page, so the only incident record here is what Resend declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Resend declared
- 5
- On its own status page, in this window.
- Window
- 2026-09-23 to 2026-10-23
- UTC, 30 days.
Sep 24, 2026, 2:31 PM UTC to Sep 24, 2026, 3:22 PM UTC
Intermittent errors on some dashboard and API requests, impact minor
Sep 26, 2026, 6:29 AM UTC to Sep 26, 2026, 9:15 AM UTC
Delayed function processing , impact minor
Oct 1, 2026, 12:28 PM UTC to Oct 1, 2026, 1:20 PM UTC
Resend API with elevated error rate, impact minor
Oct 9, 2026, 9:47 PM UTC to Oct 9, 2026, 10:10 PM UTC
Delayed new team provisioning and contact webhook delivery, impact minor
Oct 10, 2026, 2:35 PM UTC to Oct 10, 2026, 3:09 PM UTC
Delayed new team provisioning and contact webhook delivery, impact minor
Methodology
These incidents come from Resend's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Resend owes, if any, is decided under its own SLA.