Brevo: Delay sending emails

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 4h 48m it lasted.
Anything that failed between 2026-10-07 07:15 UTC and 2026-10-07 12:03 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.

investigatingOct 7, 2026, 7:15 AM UTC
We’ve detected an issue affecting sending emails. As a result, some customers may see emails delayed by 6 to 8 minutes. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for the inconvenience and will share further updates as soon as we have more information.
provider
monitoringOct 7, 2026, 7:37 AM UTC
We have mitigated the impact and are seeing no delays now. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.
provider
resolvedOct 7, 2026, 12:03 PM 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

Reports count in aggregate; nothing about you is shown.

None so far.

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

Is Brevo still down?

No, this incident was resolved 2026-10-07 12:03 UTC. For Brevo's live state, see https://down.guide/brevo.

How long did it last?

4h 48m, from 2026-10-07 07:15 UTC to 2026-10-07 12:03 UTC, by the times Brevo posted.

What caused it?

Brevo hasn't published a root cause. If it does, it shows here.

Where does this come from?

Brevo's official status page, https://status.brevo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.