Is Resend down?

Last checked 4m ago
Current status
Resend is up

No incidents right now.

Official status page: https://resend-status.com · Polled every 5 minutes · 9 components tracked

Resend is operational right now. Last checked 4m ago; the most recent incident resolved 10d ago.

Real-time Resend status, recent outages, and incident history — pulled directly from Resend's official status page at https://resend-status.com every 5 minutes. Pingoru tracks 9 Resend services and has captured 31 incidents in the last 90 days (91.23% uptime). Get email, Slack, Discord, or webhook alerts the moment Resend reports a new incident — free for 5 monitors, no credit card.

Users who monitor Resend also follow these Email services: SendGrid Calendly SparkPost Exclaimer Mailjet Front sendwithus Proton Mail Virtru mailprotector View all 6,000+ providers
Resend uptime 91.23% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 03, 2026, 04:15 PM UTC · Resolved Jun 03, 2026, 04:15 PM UTC
    Batch EmailsSingle EmailBroadcast Emails
    Timeline · 3 updates
    • identified · Jun 03, 2026, 03:45 PM UTC

      Status: Identified We are currently reverting a change that cause quotas to be calculated incorrectly. Affected components Single Email (Degraded performance) Broadcast Emails (Degraded performance) Batch Emails (Degraded performance)

    • monitoring · Jun 03, 2026, 04:10 PM UTC

      Status: Monitoring The fix has been pushed and we are now monitoring the situation. Affected components Single Email (Degraded performance) Broadcast Emails (Degraded performance) Batch Emails (Degraded performance)

    • resolved · Jun 03, 2026, 04:15 PM UTC

      Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Single Email (Operational) Broadcast Emails (Operational) Batch Emails (Operational)

    Latest: Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Single Email (Operational) Broadcast Emails (Operational) Batch Emails (Ope…

  2. Resolved
    Started May 26, 2026, 03:36 PM UTC · Resolved May 26, 2026, 03:36 PM UTC
    Batch EmailsGeneral APIEmail EventsWebhooksWebsiteDashboardSingle EmailSMTPBroadcast Emails
    Timeline · 2 updates
    • investigating · May 26, 2026, 03:29 PM UTC

      Status: Investigating We are currently investigating increased latency in Resend dashboard. At this time, you may experience delays and errors while trying to access our dashboard. Affected components Single Email (Operational) Dashboard (Full outage) SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational) General API (Operational) Webhooks (Operational) Website (Operational) Email Events (Operational)

    • resolved · May 26, 2026, 03:36 PM UTC

      Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Batch Emails (Operational) General API (Operational) Webhooks (Operational) Single Email (Operational) Dashboard (Operational) Website (Operational) Email Events (Operational) SMTP (Operational) Broadcast Emails (Operational)

    Latest: Status: Resolved We have resolved the underlying issue and service has been resumed. Affected components Batch Emails (Operational) General API (Operational) Webhooks (Operational)…

  3. Resolved
    Started May 08, 2026, 05:47 PM UTC · Resolved May 08, 2026, 05:47 PM UTC
    Batch EmailsGeneral APIEmail EventsWebhooksWebsiteDashboardSingle EmailSMTPBroadcast Emails
    Timeline · 2 updates
    • identified · May 07, 2026, 02:54 PM UTC

      Status: Identified A recent change to how Resend processes inbound emails affected customers who receive emails via server-side forwarding rules, where a mail server automatically redirects an email to a different address without rewriting its headers. When an email is forwarded this way to a Resend inbound address, the to field in the inbound webhook payload began reflecting the original "To" header (e.g. [email protected]) rather than the address that actually received the delivery (e.g. your Resend inbound address). Direct emails and client-side forwards were not affected. Affected components SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational) Webhooks (Degraded performance) Single Email (Operational) Dashboard (Operational) Email Events (Operational) General API (Operational) Website (Operational)

    • resolved · May 08, 2026, 05:47 PM UTC

      Status: Resolved We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed. Affected components Single Email (Operational) Dashboard (Operational) General API (Operational) Webhooks (Operational) Email Events (Operational) SMTP (Operational) Broadcast Emails (Operational) Batch Emails (Operational) Website (Operational)

    Latest: Status: Resolved We have resolved the underlying issue by reverting the unintended breaking change and service has been resumed. Affected components Single Email (Operational) Dash…

  4. Resolved
    Started May 06, 2026, 10:48 AM UTC · Resolved May 06, 2026, 10:48 AM UTC
    Timeline · 3 updates
    • investigating · May 06, 2026, 09:57 AM UTC

      Status: Investigating Since 09:45 UTC on May 5, 2026, new customers are unable to create custom tracking domains. Existing tracking domains and email sending are not affected. We've identified the cause as an upstream infrastructure limit and are working with our provider to resolve it.

    • monitoring · May 06, 2026, 10:22 AM UTC

      Status: Monitoring Issue identified and resolved for new requests. New customers can now create custom tracking domains again. We're replaying the failed provisioning requests from the outage window. This may take some time to fully process.

    • resolved · May 06, 2026, 10:48 AM UTC

      Status: Resolved This incident is resolved. All failed provisioning requests have been reprocessed, and custom tracking domain creation is operating normally.

    Latest: Status: Resolved This incident is resolved. All failed provisioning requests have been reprocessed, and custom tracking domain creation is operating normally.

  5. Resolved
    Started Apr 28, 2026, 08:01 PM UTC · Resolved Apr 28, 2026, 08:01 PM UTC
    Email Events
    Timeline · 4 updates
    • investigating · Apr 28, 2026, 07:17 PM UTC

      Status: Investigating We are currently investigating a delay in updating of email events. Emails are being sent/delivered, though the events may display as Queued. Affected components Email Events (Degraded performance)

    • identified · Apr 28, 2026, 07:17 PM UTC

      Status: Identified We've identified the cause of the delay in email events. Event statuses are beginning to catch up. Emails continue to be sent and delivered as normal. Only the displayed status was affected. Affected components Email Events (Degraded performance)

    • monitoring · Apr 28, 2026, 07:29 PM UTC

      Status: Monitoring We've deployed a fix for the delayed events. Webhook deliveries and email event statuses have caught up and are updating in real time. We're monitoring to confirm the fix holds. Affected components Email Events (Degraded performance)

    • resolved · Apr 28, 2026, 08:01 PM UTC

      Status: Resolved This incident is resolved. Webhook deliveries and metrics page updates have been stable since our fix was deployed. Sending and receiving were unaffected throughout. Thanks for your patience. Affected components Email Events (Operational)

    Latest: Status: Resolved This incident is resolved. Webhook deliveries and metrics page updates have been stable since our fix was deployed. Sending and receiving were unaffected throughou…

See the full Resend outage history

23 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Resend outage history →

Or sign up free to get alerts when Resend breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 28 incidents View full outage history →