Delayed transactional email delivery

What to do

• Check whether your product depends on Brevo. 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 2m it lasted.

  Anything that failed between 2026-10-05 07:18 UTC and 2026-10-05 07:20 UTC may need a replay.

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

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

Updates from Brevo 3

1. investigatingOct 5, 2026, 7:18 AM UTC

   Between 07:00 UTC and 07:08 UTC transactional emails were delivered with a delay of approximately 8 minutes. The delay was caused by connectivity errors with an internal component of our transactional sending pipeline. Affected messages were queued and delivered once connectivity was restored — no messages were lost. Delivery latency has returned to normal.

   provider

2. identifiedOct 5, 2026, 7:19 AM UTC

   We have identified the cause of the issue affecting some services. Our team is working on implementing a fix to mitigate the impact. We will continue to share updates as we progress toward resolution.

   provider

3. resolvedOct 5, 2026, 7:20 AM UTC

   The issue has been resolved, and all affected services are now functioning normally. Thank you for your patience while we worked to address the issue.

   provider

Corrections

None so far.

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