Contact webhook events are delayed in delivery

What to do

• Check whether your product depends on Resend. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 14h 9m it lasted.

  Anything that failed between 2026-08-18 19:53 UTC and 2026-08-19 10:01 UTC may need a replay.

• Subscribe to Resend's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=resend works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Resend 6

1. investigatingAug 18, 2026, 7:53 PM 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.

   provider

2. identifiedAug 18, 2026, 9:11 PM 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.

   provider

3. monitoringAug 18, 2026, 10:33 PM 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.

   provider

4. monitoringAug 18, 2026, 11:01 PM 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.

   provider

5. monitoringAug 19, 2026, 1:06 AM 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.

   provider

6. resolvedAug 19, 2026, 10:01 AM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.