Braze incident

Issue impacting US clusters

Minor Resolved View vendor source →

Braze experienced a minor incident on August 21, 2025 affecting Dashboard and Dashboard and 1 more component, lasting 49m. The incident has been resolved; the full update timeline is below.

Started
Aug 21, 2025, 07:15 PM UTC
Resolved
Aug 21, 2025, 08:05 PM UTC
Duration
49m
Detected by Pingoru
Aug 21, 2025, 07:15 PM UTC

Affected components

DashboardDashboardDashboardSDK Data CollectionSDK Data CollectionSDK Data CollectionSDK Data CollectionSDK Data CollectionSDK Data CollectionSDK Data Collection

Update timeline

  1. investigating Aug 21, 2025, 07:15 PM UTC

    Braze Engineers are currently investigating increased latency in the REST APIs.

  2. investigating Aug 21, 2025, 07:16 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 21, 2025, 07:23 PM UTC

    Braze Engineers continue to investigate increased latency in the REST APIs and SDK Data Collection across all US clusters.

  4. monitoring Aug 21, 2025, 07:50 PM UTC

    Braze REST and SDK services in the US were affected by a Cloudflare incident, for which Cloudflare has recently implemented a fix: https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2. We can confirm resolution and are no longer seeing latency issues. Customers may have experienced increased latency when making API calls. Error rates for these API services remained low despite the increased latency, with less than 0.02% failing due to a timeout. As our documented best practices note, customers should retry REST API calls that returned a 50x error code. Our SDK API will automatically retry and process all events; no events were lost. We will continue monitoring the situation and provide an update in 30 minutes.

  5. monitoring Aug 21, 2025, 07:54 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Aug 21, 2025, 08:05 PM UTC

    Braze Engineers have confirmed US clusters are operating within normal operational bounds. Engineers will continue to monitor service health across all US clusters. This incident has been resolved.