Live

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 update
01:1001:1001:1001:1101:11
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Braze

Resolved

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

4
DashboardSDK Data CollectionEU 02 Cluster - DashboardEU 02 Cluster - SDK Data Collection

Braze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

4

Median duration

2 h 25 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

9 h 14 min
median 2 h 25 min
90 days agoToday

Other Braze incidents

All incidents

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane