Skip to main content
Brevo

Delay in transactional events

Degraded Lasted 7h 3m · started · Brevo's page

Level
confirmed
Worst impact
Degraded
Down Index
22of 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 7h 3m it lasted.

    Anything that failed between 2026-11-02 12:35 UTC and 2026-11-02 19:38 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 4

  1. monitoring

    We’re currently experiencing an issue with transactional email events. Events such as opens and clicks may be delayed in statistics/ reports. Webhooks and automations that depend on these events are also affected. The root cause has been identified and fixed. We’re now working on clearing the backlog and closely monitoring the situation to ensure everything returns to normal.

    provider

  2. monitoring

    Events are now being processed normally, and we’re working through the remaining backlog. We continue to monitor our systems closely to ensure everything remains stable. We’ll share another update once we’ve confirmed that the backlog has been fully cleared and the issue is completely resolved.

    provider

  3. monitoring

    We’re continuing to work on clearing the backlog and reducing processing delays.

    provider

  4. 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-c2b870d803

Is Brevo still down?

No, this incident was resolved 2026-11-02 19:38 UTC. For Brevo's live state, see https://down.guide/brevo.

How long did it last?

7h 3m, from 2026-11-02 12:35 UTC to 2026-11-02 19:38 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.