Transactional APIs
Resend
Status detail
unexpected HTTP 200
30-day availability
73.63%
Downtime (30d)
0 min
Degraded (30d)
22780 min
Events (30d)
1
What this affects in your stack
A 401 from Resend is the healthy signal — gateway alive, just rejecting our unauthenticated probe. We use Resend for transactional email (verification + status-page subscriber notifications). If Resend is down, expect delayed or failed delivery — your customers will see "didn't receive verification email" support tickets.
email
Incident history (last 30 days)
| When | Type | Severity | Duration | Detail |
|---|---|---|---|---|
| 2026-05-21 01:35 | degraded | P2 | ongoing | HTTP 200 |
Quick links
Others in Transactional APIs
Get alerted the moment Resend has an issue (and on your own services too)
ITIL Sidekick monitors every service you depend on with multi-sample consensus probing, full HTTP capture, and a cost ledger that tracks downtime impact in real time. 60-day trial, no credit card.
Start your free trial →