Dashboard Latency and Errors on US07
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.
The latest update from Braze.
State
Resolved
Started
60 d ago
2026-09-02 11:30 UTC
Lasted
28 min
until 2026-09-02 11:58 UTC
Worst impact
Degraded
Timeline
2 updatesIdentified
28 min 100%
Updates
Times in UTCAs posted by Braze
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.
We are investigating intermittent errors and latency impacting the US07 Dashboard.
Affected components
2Braze in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
3
Median duration
2 h 3 min
This incident
77% shorter than the median
Other Braze incidents
All incidents
Braze·Braze Support Services 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.
Braze·Latency and Errors on US07
The Dashboard has continue to remain stable and the issue is now resolved.
Braze·Issue Impacting US 01 and US 03
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.
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.
https://outages.cc/feed.xml?providers=braze/feed subscribe https://outages.cc/feed.xml?providers=brazeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane