Skip to main content
Braze

Outbound email latency for non-EU Bird (Sparkpost) customers

Degraded Lasted 25m · started · Braze's page

Level
confirmed
Worst impact
Degraded
Components
Email
Regions
eu, us

What to do

  • Check whether you use Braze Email in eu, us. 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 25m it lasted.

    Anything that failed between 2026-02-24 19:34 UTC and 2026-02-24 20:00 UTC may need a replay.
  • Subscribe to Braze's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=braze works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Braze 3

  1. investigating

    Braze Engineers detected an increase in latency on email outbound messaging for customers on Bird (Sparkpost) non-EU Braze clusters. This latency build up started at 13:53 ET. Braze has engaged Sparkpost, who have declared an incident and are actively investigating, you can follow their Statuspage for updates, and we'll update here in 30 minutes, or when we learn more. https://status.sparkpost.com/incidents/ndjn00g5vwm3

    provider

  2. investigating

    As of 14:34 ET, Sparkpost has identified the root cause to be a networking issue on their US cluster. We are monitoring performance for improvement.

    provider

  3. resolved

    As of 14:41 ET, Sparkpost has declared this incident resolved after implementing a fix. Braze Engineers have confirmed that real time outbound email latency has returned within normal operational bounds as of 14:34 ET. Any messages that failed during this window, were automatically retried. This incident is considered resolved.

    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-3c9b566602

Is Braze still down?

No, this incident was resolved 2026-02-24 20:00 UTC. For Braze's live state, see https://down.guide/braze.

How long did it last?

25m, from 2026-02-24 19:34 UTC to 2026-02-24 20:00 UTC, by the times Braze posted.

What was affected?

Braze named Email in eu, us.

What caused it?

Braze hasn't published a root cause. If it does, it shows here.

Where does this come from?

Braze's official status page, https://braze.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.