The pending domain verifications and broadcasts are catching-up quickly. The incident should fully resolve soon.

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

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

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

We have resolved the issue causing increased latency in email sending. Emails are being delivered normally.

Our systems have caught up and email events are processing normally. No emails were lost or delayed during this time.

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

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

The maintenance was completed. We're working through some backlogged Email Events.

The issue has been resolved, and sending to Microsoft-owned domains has been restored.

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

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

Performance is back to normal.

Performance is back to normal.

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

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

This incident has been resolved. Email sending and dashboard performance are both operating normally. Thank you for your patience while we worked through this.

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

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

Service has been resumed.

Broadcast sending has returned to normal speed. Queue times are back to expected levels. Thank you for your patience.

It was a false alert. It was caused by a combination of an ongoing incident with the third‑party observability service we use and some internal, isolated infrastructure experiments.

Emails have been sent smoothly and there have been no delays.

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

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

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

We have resolved the underlying issue and service has been resumed. All emails that have queued have been sent.

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

The underlying issue has been identified and resolved, and services have been fully restored. Thanks for your patience while we worked through this.

Our systems have caught up with the delayed emails and are healthy again. No emails were lost during the period of degraded performance.

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

Microsoft is reporting that email is returning to normal sending, with its most recent update stating, "We have a high level of confidence that the incident is largely resolved." From our own metrics, we're also seeing "Delivery Delayed" events reduce, with deliveries now happening upon retry.

We've detected a misconfiguration on one of our load balancers which has caused 429 errors to be returned incorrectly for our APIs between 3:03 PM to 3:10 PM UTC.

Requests sent during this time returned errors because of the aforementioned reason, both on the General API, Email API and SMTP.

All systems are operating normally and no emails were lost.

We have resolved the underlying issue, and email sending has returned to normal. Thank you for your patience while we worked through this. If you have any questions or concerns, please don’t hesitate to reach out to support@resend.com.