Resend Status
System status
View historical uptime →Incident overview
Total incidents
28
Active now
0
Resolved
28
Avg. resolution
7h 35m
Recent incidents
View all →Delayed new team provisioning and contact webhook delivery
Delayed new team provisioning and contact webhook delivery
Resend API with elevated error rate
Delayed function processing
Intermittent errors on some dashboard and API requests
Failing to verify new domains
Degraded performance
Degraded performance
Increased latency in WebHooks
High latency on General-API
Frequently asked questions
Is Resend down right now?
Resend is currently operational. DevHelm monitors Resend's official status page continuously and updates this page every 5 minutes.
What is Resend's current uptime?
Resend has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from Resend's official status page data.
How many incidents has Resend had recently?
Resend has experienced 28 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 7h 35m. All incidents are currently resolved.
What components does Resend monitor?
DevHelm tracks 12 individual components for Resend, including Single Email, Batch Emails, Broadcast Emails, Scheduled Emails, SMTP, and 7 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Resend outages?
You can subscribe to Resend's incident feed via Atom/RSS at devhelm.io/status/resend/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Resend as a dependency in your DevHelm workspace.
What SLA does Resend offer?
See the full Resend SLA report at devhelm.io/sla/resend — including their official uptime guarantee, pricing tiers, credit policy, and how their measured uptime compares to their SLA commitment.
About Resend status monitoring
This page provides real-time operational status for Resend, powered by DevHelm's continuous monitoring infrastructure. We track Resend's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Resend status data is refreshed every 5 minutes. We currently track 12 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Resend in your stack
Get alerted when Resend has issues — before your users notice. Set up in 30 seconds.