We started checking Brevo on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Brevo reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Brevo's own status page declared. Below it, any public chatter we saw about Brevo and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Brevo's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Brevo in the last 24 hours, which is not evidence that nothing is wrong.
Brevo's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Brevo's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Brevo next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
432
US-West
100.00%
338
Europe
100.00%
307
Asia-Pacific
100.00%
188
Their declared record
Brevo's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delay in transactional eventsMinor incident
Nov 2, 2026, 12:35 PM UTC to Nov 2, 2026, 7:38 PM UTC (7h 3m)resolved
their latest update (Nov 2, 2026, 7:38 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.
Multiple Services ImpactedMinor incident
Oct 27, 2026, 2:37 PM UTC to Oct 27, 2026, 6:58 PM UTC (4h 21m)resolved
their latest update (Oct 27, 2026, 6:58 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.
Error with doubleOptinConfirmation APIMinor incident
Oct 26, 2026, 5:31 AM UTC to Oct 26, 2026, 7:41 AM UTC (2h 11m)resolved
their latest update (Oct 26, 2026, 7:41 AM UTC): We’ve updated the error message to make it clearer and more intuitive for clients. The API requests should not be blocked after following the recommended step in the error message.
Issue with plan purchaseAll systems operational
Oct 22, 2026, 6:10 PM UTC to Oct 22, 2026, 8:05 PM UTC (1h 55m)resolved
their latest update (Oct 22, 2026, 8:05 PM UTC): The issue has been resolved, and plan purchase should now function normally.
Thank you for your patience while we worked to address the issue.
Elevated error on public APIMinor incident
Oct 19, 2026, 2:47 PM UTC to Oct 19, 2026, 3:06 PM UTC (20 min)resolved
their latest update (Oct 19, 2026, 3:06 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.
Multiple Services ImpactedMinor incident
Oct 15, 2026, 11:00 PM UTC to Oct 15, 2026, 11:10 PM UTC (10 min)resolved
their latest update (Oct 15, 2026, 11:10 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.
Delay in Processing Loyalty API requestMinor incident
Oct 15, 2026, 4:34 AM UTC to Oct 15, 2026, 4:46 AM UTC (12 min)resolved
their latest update (Oct 15, 2026, 4:46 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.
Multiple Services ImpactedMinor incident
Oct 14, 2026, 4:14 PM UTC to Oct 14, 2026, 4:47 PM UTC (33 min)resolved
their latest update (Oct 14, 2026, 4:47 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.
Delays on Transactional Email Delivery and PreviewMinor incident
Oct 14, 2026, 8:26 AM UTC to Oct 14, 2026, 8:32 AM UTC (6 min)resolved
their latest update (Oct 14, 2026, 8:32 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.
Delays in event processing affecting automationsMinor incident
Oct 7, 2026, 3:37 PM UTC to Oct 7, 2026, 6:23 PM UTC (2h 46m)resolved
their latest update (Oct 7, 2026, 6:23 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.
Showing the 10 most recent of 25 incidents Brevo has declared in the history we hold.
These entries are Brevo's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Brevo's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.