Resend incident

Custom tracking domains failing to provision for new customers

Minor Resolved View vendor source →

Resend experienced a minor incident on May 6, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 10:48 AM UTC
Resolved
May 06, 2026, 10:48 AM UTC
Duration
Detected by Pingoru
May 06, 2026, 10:48 AM UTC

Update timeline

  1. 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.

  2. 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.

  3. 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.

Looking to track Resend downtime and outages?

Pingoru polls Resend's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Resend reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Resend alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Resend for free

5 free monitors · No credit card required