Companies / Braze / changes

Braze change history

14Major incident
When (UTC)ChangeKind
Critical incident: Braze Support Services Outage
Braze reported a critical Support Services and Partner Portal outage from 2026-09-16 09:17 UTC to 2026-09-16 16:09 UTC, lasting 6 h 51 min. A Salesforce Service Cloud incident disrupted case submissions through the Braze Support Portal and Braze AI Operator and could delay responses; service was restored following remediation of the underlying issue.
Major incident
Major incident: Issue impacting EU01
Braze reported a major EU01 degradation affecting Dashboard, Data Processing, Outbound Messaging, REST APIs and SDK Data Collection, starting 2026-04-20 16:18 UTC and resolved at 2026-04-20 19:24 UTC (3 h 5 min). Message backlog and latency degraded data processing; Braze cleared the backlog and confirmed normal processing and stable services.
Major incident
Major incident: Delays in Support Case Creation via Email
Braze reported a major support-email degradation from 2026-04-08 19:05 UTC to 2026-04-08 21:49 UTC, lasting 2 h 43 min: new cases and replies were not processed. Braze attributed the issue to a Google Workspace incident and also reported Salesforce Email-to-Case issues. Processing resumed; support was clearing the backlog, with the Support Portal offered as an alternative.
Major incident
Major incident: US05 Dashboard latency
Braze reported a major US05 Dashboard outage affecting users’ ability to reach the dashboard, starting 2026-03-17 20:49 UTC and resolved at 2026-03-17 21:04 UTC (15 min). Engineers implemented a fix; messaging sending and other services were not impacted.
Major incident
Critical incident: US02 Dashboard and SDK increased errors
Braze reported a critical incident affecting the US02 Dashboard and SDK Data Collection, with increased errors and possible Dashboard timeouts. The incident started at 2026-02-03 15:41 UTC and was resolved at 2026-02-03 16:02 UTC, lasting 21 min. Services were restored; the SDK automatically retries failed requests, and no action is required.
Major incident
Critical incident: US05 Dashboard Errors
Braze reported a critical incident causing errors accessing the US05 Cluster Dashboard, starting 2026-01-06 15:41 UTC and resolved at 2026-01-06 16:29 UTC (47 min). Messaging sending and other services were unaffected. Dashboard service was restored and monitored before resolution.
Major incident
Major incident: EU01 REST API and SDK Data Collection Errors
Braze reported a major EU01 incident affecting REST APIs and SDK Data Collection from 2025-11-24 11:26 UTC to 2025-11-24 12:09 UTC, lasting 43 min. Elevated errors subsided by 11:51 UTC; customers must retry REST API requests that received errors.
Major incident
Major incident: US01 and US03 Dashboard and SDK Errors
Braze reported a major incident affecting US01 and US03 Dashboard and SDK services, with Data Processing and SDK Data Collection listed as affected components. It started at 2025-11-19 00:34 UTC and was resolved at 2025-11-19 01:33 UTC, lasting 59 min. Engineers implemented a fix and confirmed services were operating normally.
Major incident
Major incident: AWS US East 1 outage
Braze reported a major AWS US East 1 outage starting 2025-10-20 16:21 UTC, resolved 2025-10-20 23:41 UTC. AWS capacity shortages delayed Data Processing and Outbound messaging on US03 and US05; affected Twilio services disrupted SMS authentication and messaging. Engineers load-balanced work and cleared backlogs; Twilio recovered.
Major incident
Major incident: Issue impacting US01 and US05 clusters
Braze reported a major degradation on US01 and US05, with increased latency and dashboard errors; other services were not impacted. The incident started at 2025-09-02 17:20 UTC and was resolved at 2025-09-02 17:45 UTC, lasting 25 min.
Major incident
Major incident: Issue impacting US06 AND EU02 services
Braze reported a major outage affecting Dashboard, REST APIs, and SDK Data Collection in US06 and EU02, starting at 2025-08-19 14:40 UTC and lasting 1 h 1 min. Fixes restored both clusters, and the incident was resolved at 2025-08-19 15:41 UTC; Braze said it identified the root cause but did not specify it.
Major incident
Major incident: Link-shortening issue impacting all regions
Braze reported a major link-shortening outage across all regions starting 2025-07-17 20:22 UTC, delaying SMS and WhatsApp messages with shortened or tracked URLs and causing HTTP 500 errors on clicks. Service was restored and the message backlog cleared; the incident was resolved at 2025-07-17 21:12 UTC after 50 min.
Major incident
Major incident: Widespread Internet Issue
Braze reported major degradation from 2025-06-12 19:01 UTC to resolution at 2025-06-12 21:30 UTC: message sending and data processing latency, SDK API errors, and disrupted Android push delivery. The Google Cloud outage prevented Kubernetes scaling; infrastructure later scaled up to process backlogs, and Google confirmed Android Push / Firebase messaging recovery.
Major incident
Major incident: Currents and CDI latency impacting EU-01 and EU-02
Braze reported major Currents and CDI latency in EU-01 and EU-02 due to an infrastructure problem, starting 2025-03-10 15:47 UTC and resolved at 2025-03-10 22:21 UTC (6 h 33 min). New events and CDI syncs returned to normal, but the Currents event backlog was still being processed; outbound messaging operated normally.
Major incident