Braze incident

US05 Processing Latency

Minor Resolved View vendor source →

Braze experienced a minor incident on May 8, 2026 affecting Dashboard and SDK Data Collection and 1 more component, lasting 1h 11m. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 04:35 AM UTC
Resolved
May 08, 2026, 05:47 AM UTC
Duration
1h 11m
Detected by Pingoru
May 08, 2026, 04:35 AM UTC

Affected components

DashboardSDK Data CollectionData ProcessingOutbound Messaging

Update timeline

  1. identified May 08, 2026, 04:35 AM UTC

    Starting at 11:45 PM ET, Braze customers on our US05 have been experiencing latency across campaign/canvas processing, data processing, and message sending due to an ongoing issue with an upstream provider (AWS). We are working on a fix. Please see https://health.aws.amazon.com/health/status for more details.

  2. identified May 08, 2026, 05:04 AM UTC

    We are continuing to experience delays in Campaign & Canvas Processing, Data Processing, and Message Sending. Additionally, Dashboard navigation is intermittently erroring. We are continuing to work on a fix while we await updates from AWS. Please see https://health.aws.amazon.com/health/status for more details.

  3. monitoring May 08, 2026, 05:32 AM UTC

    We have implemented a fix to mitigate the impact of the ongoing AWS incident in Availability Zone (use1-az4) in the US-EAST-1 region. At this point, latency and error rates have returned to normal levels for all services. Additionally, AWS is reporting early signs of recovery. Please see https://health.aws.amazon.com/health/status for more details.

  4. resolved May 08, 2026, 05:47 AM UTC

    Latency and error rates have remained at normal levels for all services, post-implementation of our fix, and this incident is resolved. We will continue to monitor the overall system health until AWS reports full recovery. Please see https://health.aws.amazon.com/health/status for more details.