EU02 SDK and Dashboard Errors
On November 16, 2026, from 00:19 to 00:42 UTC, customers on the EU-02 cluster may have experienced errors in the Braze dashboard. SDK requests may have also experienced errors during this window. The Braze SDK retries failed requests automatically, so no action is required. The cause was an issue with a database that serves the EU-02 cluster.
The latest update from Braze.
State
Resolved
Started
Lasted
1 min
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Braze
On November 16, 2026, from 00:19 to 00:42 UTC, customers on the EU-02 cluster may have experienced errors in the Braze dashboard. SDK requests may have also experienced errors during this window. The Braze SDK retries failed requests automatically, so no action is required. The cause was an issue with a database that serves the EU-02 cluster.
Affected components
4Braze in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
4
Median duration
2 h 25 min
This incident
100% shorter than the median
Other Braze incidents
All incidents
Braze·Email Delivery delays to Microsoft inboxes
Email delivery from Braze to Microsoft-hosted inboxes was delayed. This affected outlook.com, hotmail.com, live.com, and Microsoft 365 business domains in all regions. Braze reports that the incident is resolved. The outage lasted about 9 hours and 14 minutes.

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·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.

Braze·Latency and Errors on US07
The Dashboard has continue to remain stable and the issue 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.live/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.live/feed.xml?providers=braze/feed subscribe https://outages.live/feed.xml?providers=brazeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane