Skip to main content

Is Brevo Down?

No — Brevo is up

Reachable from all 8 checked regions

Average response time: 358ms

Last checked · checks run every 6 hours

Official status page: https://status.brevo.com

Brevo uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
183ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 16 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: 100.00% uptime, 16 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 40 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 40 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 31 checks
Aug 22: 100.00% uptime, 31 checks
Aug 23: 100.00% uptime, 24 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
43ms
DNS 0ms TCP 2ms TLS 10ms TTFB 27ms
arn
35ms
DNS 0ms TCP 1ms TLS 8ms TTFB 25ms
bom
2591ms
DNS 0ms TCP 3ms TLS 13ms TTFB 2573ms
cdg
42ms
DNS 2ms TCP 1ms TLS 7ms TTFB 28ms
ord
47ms
DNS 0ms TCP 2ms TLS 8ms TTFB 30ms
sin
35ms
DNS 0ms TCP 1ms TLS 8ms TTFB 24ms
sjc
60ms
DNS 0ms TCP 4ms TLS 13ms TTFB 40ms
syd
32ms
DNS 0ms TCP 1ms TLS 7ms TTFB 21ms
yyz
32ms
DNS 0ms TCP 1ms TLS 6ms TTFB 24ms

What Brevo does

Brevo, formerly Sendinblue, is a marketing and customer relationship platform combining email campaigns, transactional email and SMS, automations, a CRM and live chat. Developers use its transactional API to send password resets, receipts and notifications, so it becomes a dependency for sign-up and checkout flows rather than only a marketing tool. Small and mid-sized businesses are its main audience.

What an outage looks like

Brevo groups its status page into Marketing, Transactional, Automations, CRM, Conversations, Commerce, Integrations, its Customer Data Platform and Account and Settings. A transactional fault is the one users notice fastest: password resets and receipts stop arriving while the dashboard looks fine. Campaign sends can stall mid-delivery, automations can stop triggering, and login or dashboard access can fail on its own.

What to do about it

Check status.brevo.com and identify which group is affected, because Transactional and Marketing are reported separately and most people only care about one of them. Transactional email queued during an incident is generally delivered late rather than dropped, so resending risks duplicates. If password resets are the problem, tell users the delay is upstream before they request more and compound the queue.

Is it down for everyone, or just you?

If this page says Brevo is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Brevo outage FAQ

My password reset emails are not arriving. Is Brevo down?
Possibly. Transactional is a separate component group from Marketing on Brevo's status page, and a transactional incident stops exactly this kind of message while campaigns and the dashboard appear healthy. Check that group specifically. If Brevo is operational, the more common causes are the receiving provider's spam filtering or a sending domain authentication problem on your side.
Will my scheduled campaign still send if Brevo has an outage?
Scheduled sends are queued by Brevo rather than triggered from your own system, so a campaign scheduled during an incident is usually delayed rather than cancelled. The risk is duplication: rescheduling a send that was only stalled can deliver twice. Wait for the Marketing components to show operational, then check the campaign's own send report before intervening.
Does a Brevo outage affect the CRM and chat as well as email?
Not automatically. Brevo tracks CRM, Conversations, Commerce and its Customer Data Platform as separate component groups from Marketing and Transactional. Live chat can be down while email sends fine, or the reverse. The grouping is the most useful part of Brevo's status page during an incident, because it tells you which half of the platform to stop relying on.
Are contacts or campaign data lost during an outage?
Stored contacts, lists and campaign history are not removed by an availability incident. What is at risk is data being written during the outage: contacts synced through the API or an integration may fail to apply and need re-sending. Integrations is its own component group, so check it separately if a sync appears to have silently skipped records.

How we measure this

  • We request Brevo's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Brevo publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Brevo goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required