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.
The latest update from Braze.
State
Resolved
Started
47 d ago
2026-09-16 09:17 UTC
Lasted
6 h 52 min
until 2026-09-16 16:09 UTC
Worst impact
Major outage
Timeline
3 updatesIdentified
6 h 23 min 93%
Monitoring
28 min 7%
Updates
Times in UTCAs posted by Braze
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.
We are observing signs of resolution, and at this time, customers are able to use our Global Support Service normally. We continue to monitor the service while Salesforce continues remediation of the Salesforce Service Cloud issue. Customers can now raise cases via the Braze Support Portal and the Braze AI Operator as usual.
Braze Support Services and Partner Portal are currently experiencing issues due to an incident impacting Salesforce Service Cloud. Customers may experience issues when submitting cases via the Braze Support Portal and Braze AI Operator. During this time, you may also experience delays in response to support cases. For any critical cases, please contact support@braze.com.
Affected components
2Follow 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