Resend

Probed every 300s · last check 8m ago

Degraded

Status detail

unexpected HTTP 200

30-day availability

99.93%

Downtime (30d)

30 min

Degraded (30d)

32338 min

Events (30d)

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.

Incident history (last 30 days)

When	Type	Severity	Duration	Detail
2026-08-18 01:10	degraded	P2	ongoing	HTTP 200
2026-08-18 01:00	down	P0	9m	timeout
2026-08-06 18:10	degraded	P2	270h 50m	HTTP 200
2026-08-06 18:00	down	P0	9m	timeout
2026-08-03 01:25	degraded	P2	88h 34m	HTTP 200
2026-08-03 01:15	down	P0	9m	timeout

Quick links

Official status page ↗ Documentation ↗ Vendor homepage ↗ JSON API ↗

Others in Transactional APIs

Stripe Twilio SendGrid Slack Discord OpenAI Anthropic (Claude)

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 →

Embed this provider's status on your site

<iframe src="https://itilsidekick.com/internet-weather/embed?provider=resend"
        width="100%" height="200" frameborder="0" loading="lazy"
        title="Live Resend status by ITIL Sidekick"></iframe>