Skip to main content
Brevo

Delay in Processing Loyalty API request

Degraded Lasted 12m · started · Brevo's page

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

    Anything that failed between 2026-10-15 04:34 UTC and 2026-10-15 04:46 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. investigating

    We’ve detected an issue affecting the Loyalty API, which may be causing disruptions for some customers using the service. 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 provide further updates as soon as more information becomes available.

    provider

  2. identified

    We have identified the root cause of the issue affecting the Loyalty API Endpoints, which may be causing disruptions for some customers using the service. Our team is actively working on implementing a fix to mitigate the impact and restore the service as quickly as possible. We will continue to provide updates as we make progress toward resolution.

    provider

  3. monitoring

    We have mitigated the impact of the issue affecting the Loyalty API and are seeing a reduction in errors across the affected services. Our team continues to monitor the systems closely to ensure stability and confirm that the issue is fully resolved. We will provide a further update once the issue is confirmed to be fully resolved.

    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-a2a7f1cd9c

Is Brevo still down?

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

How long did it last?

12m, from 2026-10-15 04:34 UTC to 2026-10-15 04:46 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.