Resend incident: Contact webhook events are delayed in delivery

1. resolvedAug 19, 2026, 10:01 UTC

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

2. monitoringAug 19, 2026, 01:06 UTC

   We have processed more than 66% of the backlog at this point. Within the next hour, the backlog will be fully processed, and this incident will be marked as resolved.

3. monitoringAug 18, 2026, 23:01 UTC

   We are still monitoring the progress on processing the backlog. The impact has been reduced from a peak 3-hour delay in delivering a contact webhook to 2h 20 min. The delay is being reduced further as we process the backlog. Within 2-3 hours, the backlog will be completely processed.

4. monitoringAug 18, 2026, 22:33 UTC

   A fix has been deployed to the underlying infrastructure and we can now confirm we're processing the backlog with the correct volume. Delayed webhooks are now being delivered. We will post another update in 30 minutes to share more about the progress on processing the backlog.

5. identifiedAug 18, 2026, 21:11 UTC

   We have identified the issue and are working on mitigating its effects. The volume of contact webhooks processed over time was affected by an infrastructure change, and now we have an increasing backlog of contact webhooks to process. The team is working on increasing the speed of processing the backlog. No contact webhooks were lost.

6. investigatingAug 18, 2026, 19:53 UTC

   We are currently investigating increased latency in contact webhook delivery. We have noticed a delay of approximately 50 minutes in sending webhooks related to contact events. The team is investigating and mitigating this processing delay issue. Contact management via dashbaord and its API are not affected.

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.

• Netlify: Elevated HTTP 500 errors serving sites and the Netlify UICritical · Aug 18, 2026, 20:00 UTC
• Grafana Cloud: Cloud Logs read path outage on eu-west-2Critical · Aug 18, 2026, 22:53 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Akamai: Connection drops and increased latency in MiamiMinor · Aug 13, 2026, 19:31 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
• Expo: iOS Submissions hanging on App Store Connect build uploadsMinor · Aug 18, 2026, 16:25 UTC
• Cursor: Grok Bot connector delaysMinor · Aug 18, 2026, 18:46 UTC
• Cursor: GitHub-connected Cloud Agent workflows degradedMinor · Aug 18, 2026, 19:47 UTC
• Sentry: Alert backlogs in USMinor · Aug 18, 2026, 21:42 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