Resend incident: Degraded performance

1. resolvedSep 20, 2026, 18:27 UTC

   We have resolved the underlying issue and service has been resumed.

2. resolvedSep 20, 2026, 18:26 UTC

   We have resolved the underlying issue and service has been resumed.

3. monitoringSep 18, 2026, 18:34 UTC

   Services recovered and we are now monitoring the situation.

4. investigatingSep 18, 2026, 18:26 UTC

   We are currently investigating increased latency webhooks, account creation/confirmation and domain provisioning.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Resend's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Inngest: Degraded Function ExecutionMajor · Sep 18, 2026, 16:31 UTC
• Cursor: Investigating service degradation — Grok BotMajor · Sep 18, 2026, 17:19 UTC
• Vercel: Elevated Errors Triggering DeploymentsMajor · Sep 18, 2026, 20:32 UTC
• dbt Cloud: Schema Hydration PanicMajor · Sep 18, 2026, 23:31 UTC
• ElevenLabs: Some ElevenAgents calls failed to startMajor · Sep 19, 2026, 00:34 UTC
• Supabase: Project Lifecycle Activity DegradationMajor · Sep 19, 2026, 20:12 UTC
• Shippo: Elevated error rate on Canada Post Shipment APIMajor · Sep 20, 2026, 05:56 UTC
• Shippo: Axlehire tracking disruptionsMajor · Sep 20, 2026, 12:17 UTC
• Twilio: Voice Call Failures from a Subset of Twilio Phone Numbers to Hong KongMinor · Sep 12, 2026, 00:16 UTC
• Notion: Some connected content results unavailable in Notion AIMinor · Sep 17, 2026, 14:07 UTC

How often does Resend have incidents?

Resend reported 23 incidents in the last 90 days, 6 of them major or critical. A typical incident lasted 43 min. See Resend's uptime and incident history