Resend incident: Increased latency across API endpoints

1. resolvedAug 20, 2026, 05:22 UTC

   We have resolved the underlying issue and service latency has been recovered.

2. identifiedAug 20, 2026, 05:17 UTC

   We have identified the issue and deployed a fix. API latency has recovered since then. Our team is still monitoring to ensure it remains stable over the next few minutes.

3. investigatingAug 20, 2026, 04:58 UTC

   We are currently investigating increased latency in non-email sending API endpoints. Our team is investigating it.

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.

• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 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