Skip to main content
Brevo

Issue with Ecommerce orders

Major outage Lasted 11m · started · Brevo's page

Level
confirmed
Worst impact
Major outage
Down Index
36of 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 11m it lasted.

    Anything that failed between 2026-10-07 12:21 UTC and 2026-10-07 12:32 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.

Root cause

Our team is actively investigating the root cause and working to resolve the issue as quickly as possible.
Read the postmortem

Updates from Brevo 3

  1. investigating

    We’ve detected an issue affecting Ecommerce orders, and as a result, some customers may be experiencing disruptions while using it. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We apologize for the inconvenience and will share further updates as soon as we have more information.

    provider

  2. monitoring

    We have mitigated the impact and are seeing a reduction in errors across the affected services. We continue to monitor our systems closely to ensure stability. We’ll provide an update once we confirm the issue is fully resolved.

    provider

  3. 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-8315a825e5

Is Brevo still down?

No, this incident was resolved 2026-10-07 12:32 UTC. For Brevo's live state, see https://down.guide/brevo.

How long did it last?

11m, from 2026-10-07 12:21 UTC to 2026-10-07 12:32 UTC, by the times Brevo posted.

What caused it?

Brevo wrote: "Our team is actively investigating the root cause and working to resolve the issue as quickly as possible." The postmortem: https://status.brevo.com/incidents/01M4B4YQHBGEA5GNM1J2CEJ7CZ

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.