Skip to content

Incident detail

Contact webhook events are delayed in delivery

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Resend breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Resend posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    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.

  2. Identified

    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.

  3. Monitoring

    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.

  4. Monitoring

    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.

  5. Monitoring

    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.

  6. Resolved

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

Keep exploring

More from Resend

Neighboring incidents on Resend's timeline and the rest of their record on OutageDeck.