outages.live
Live
B

Braze

Braze is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

4

Days with an incident

3

Median duration

2 h 3 min

Longest incident

6 h 52 min

Components

115

US 01 Cluster

Dashboard Operational
90 days ago1 day with an incidentToday
SDK Data Collection Operational
90 days agoNo incidentsToday
Data Processing Operational
90 days agoNo incidentsToday
REST APIs Operational
90 days ago1 day with an incidentToday
Outbound Messaging Operational
90 days agoNo incidentsToday
Currents Operational
90 days agoNo incidentsToday
Cloud Data-Ingestion (CDI) Operational
90 days agoNo incidentsToday

US 02 Cluster

Dashboard Operational
90 days agoNo incidentsToday
SDK Data Collection Operational
90 days agoNo incidentsToday
Data Processing Operational
90 days agoNo incidentsToday
REST APIs Operational
90 days agoNo incidentsToday
Outbound Messaging Operational
90 days agoNo incidentsToday
Currents Operational
90 days agoNo incidentsToday
Cloud Data-Ingestion (CDI) Operational
90 days agoNo incidentsToday

US 03 Cluster

Dashboard Operational
90 days ago1 day with an incidentToday
SDK Data Collection Operational
90 days agoNo incidentsToday
Data Processing Operational
90 days agoNo incidentsToday
REST APIs Operational
90 days ago1 day with an incidentToday
Outbound Messaging Operational
90 days agoNo incidentsToday
Currents Operational
90 days agoNo incidentsToday
Cloud Data-Ingestion (CDI) Operational
90 days agoNo incidentsToday

US 04 Cluster

Dashboard Operational
90 days agoNo incidentsToday
SDK Data Collection Operational
90 days agoNo incidentsToday
Data Processing Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 16, 2026

Duration6 h 52 min09:17 to 16:09Braze Support Services OutageMajor outage

This issue has been resolved. Our Global Support Service is operating normally, and customers can raise cases via the Braze Support Portal and the Braze AI Operator as usual. We have confirmed stable service following remediation of the underlying Salesforce Service Cloud issue.

Sep 2, 2026

Duration28 min11:30 to 11:58Dashboard Latency and Errors on US07Degraded

This was a recurrence of an earlier issue impacting the Dashboard. A permanent fix has been implemented and the Dashboard has remained stable since. We are confident the issue is now fully resolved. We apologize for any impact.

Duration2 h 25 min07:43 to 10:09Latency and Errors on US07Degraded

The Dashboard has continue to remain stable and the issue is now resolved.

Aug 5, 2026

Duration1 h 41 min16:13 to 17:54Issue Impacting US 01 and US 03Degraded

Between 11:30 ET and 12:55 ET, some customers experienced elevated error rates. Braze engineers identified the issue and resolved it by rolling back a recent change and applying database optimizations. Error rates returned to normal shortly after each fix was applied, and they have remained stable for the past hour. This incident is now resolved.

Follow Braze

Your coding agent knows when Braze is down, and tells you when a failure is theirs, not yours. You can also get Braze incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "braze" and tell me if Braze has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=braze
Slack
/feed subscribe https://outages.cc/feed.xml?providers=braze

Go from tracking outages to fixing production issues with Polylane.

Try Polylane