- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 29m it lasted.
Anything that failed between 2026-09-21 09:44 UTC and 2026-09-21 12:12 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
- investigating
We have identified issue effecting our Phone and Conversations service. Some phone call history data is not complete, will be refilled soon Gmail and Outlook conversations emails are currently delayed or not delivered, both for incoming and outgoing messages. This issue affects all users of Phone and Conversations. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.
provider
- monitoring
Phone services have been restored, and Conversations are currently processing. Email processing has also resumed. Due to the large volume of emails queued during the issue, processing will take some time. We are continuing to work through the backlog and are monitoring the services as well.
provider
- resolved
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.
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-2397953fdf
Is Brevo still down?
No, this incident was resolved 2026-09-21 12:12 UTC. For Brevo's live state, see https://down.guide/brevo.
How long did it last?
2h 29m, from 2026-09-21 09:44 UTC to 2026-09-21 12:12 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.