Brevo outage, 13 November 2026

Delay in Email delivery

Started
Resolved
13 Nov 2026, 15:55 UTC (after 4 h 14 min)
Impact
Minor

Is this still happening?

No. Brevo marked this incident resolved on 13 Nov 2026, 15:55 UTC, 4 h 14 min after it began.

Right now: Brevo reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Brevo status

At a glance

Our summary from the Brevo incidents we have recorded since 30 Jul 2026 - how we count.

Last update from Brevo

Email delivery rates to Outlook are improving and have now stabilised. Upon further investigation, we identified that the Gmail delays were not caused by an issue on Gmail’s side. Instead, the backlog of pending Outlook messages increased the processing pressure on our infrastructure, impacting Gmail delivery as well. We have mitigated this issue. While some delays to Outlook may persist due to the ongoing Microsoft outage and its reduced acceptance rate, we expect email delivery across other domains to return to normal. Thank you so much for your patience.

13 Nov 2026, 15:55 UTC

Similar Brevo incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 6 min

    Delays on Transactional Email Delivery and Preview

  2. , resolved after 4 h 47 min

    Delay sending emails

  3. , resolved after 4 h 7 min

    Delays affecting email previews and "view in browser" links

  4. , resolved after 2 min

    Delayed transactional email delivery

  5. , resolved after 2 h 57 min

    Degraded performance - Contacts, campaign statistics, and email/SMS processing delays

Other recent Brevo incidents

  1. Multiple services are impacted

  2. Delay in transactional events

  3. Multiple Services ImpactedPostmortem

  4. Error with doubleOptinConfirmation API

  5. Issue with plan purchase

  6. Elevated error on public API

  7. Multiple Services Impacted

  8. Delay in Processing Loyalty API request

All recorded Brevo incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Brevo's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.