- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 29of 100
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 2h 2m it lasted.
Anything that failed between 2026-10-01 10:19 UTC and 2026-10-01 12:21 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.
Root cause
Our team is actively investigating the root cause and working to resolve the issue as quickly as possible.Read the postmortem
Updates from Brevo 3
- investigating
We’ve detected an issue affecting our SMS service that is causing soft bounces, and as a result, some customers may be experiencing disruptions while sending SMS messages. Our team is actively investigating the root cause 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
- identified
We have identified the cause of the issue affecting our SMS services. Our team is currently working on implementing a fix to mitigate the impact. We will continue to share updates as we make progress toward resolving the issue.
provider
- resolved
The issue has been resolved, and all SMS campaigns and transactional SMS will now be processed without any issues. Thank you for your patience and cooperation while we worked to address the issue.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-14be669626
Is Brevo still down?
No, this incident was resolved 2026-10-01 12:21 UTC. For Brevo's live state, see https://down.guide/brevo.
How long did it last?
2h 2m, from 2026-10-01 10:19 UTC to 2026-10-01 12:21 UTC, by the times Brevo posted.
What caused it?
Brevo wrote: "Our team is actively investigating the root cause and working to resolve the issue as quickly as possible." The postmortem: https://status.brevo.com/incidents/01M3VFM9E9RB02FYM4DJ4Q0E52
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.