outages.live
Live
Braze logoBrazeIncident · 2026-08-05 16:13 UTC

Issue Impacting US 01 and US 03

ResolvedOfficial update

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.

The latest update from Braze.

State

Resolved

Started

88 d ago

2026-08-05 16:13 UTC

Lasted

1 h 41 min

until 2026-08-05 17:54 UTC

Worst impact

Degraded

Timeline

2 updates
16:1316:3817:0317:2817:54
DegradedUpdate postedTimes in UTC

Investigating

1 h 41 min 100%

Updates

Times in UTC

As posted by Braze

Resolved2026-08-05 17:54 UTC

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.

Investigating2026-08-05 16:13 UTC

We are currently investigating an issue with the US 01 and US 03 clusters.

Affected components

6
DashboardREST APIsUS 01 Cluster - DashboardUS 01 Cluster - REST APIsUS 03 Cluster - DashboardUS 03 Cluster - REST APIs

Braze in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

3

Median duration

2 h 3 min

This incident

18% shorter than the median

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

6 h 52 min
median 2 h 3 min
90 days agoToday

Other Braze incidents

All incidents
Braze logo

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.

Resolvedresolved 46 d ago
Braze logo

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.

Resolvedresolved 60 d ago
Braze logo

Braze·Latency and Errors on US07

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

Resolvedresolved 61 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane