- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Braze. 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 0m it lasted.
Anything that failed between 2026-01-13 22:19 UTC and 2026-01-13 21: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 1
- resolved
Between 4:05 PM and 4:58 PM ET, some SMS messages experienced a temporary delivery delay. The issue has been fully resolved. All delayed messages were safely queued and are now being delivered. No messages were lost. Our systems are operating normally, and our team is monitoring to ensure continued stability.
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-93fb97df29
Is Braze still down?
No, this incident was resolved 2026-01-13 21:00 UTC. For Braze's live state, see https://down.guide/braze.
How long did it last?
0m, from 2026-01-13 22:19 UTC to 2026-01-13 21:00 UTC, by the times Braze posted.
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.