AWS Networking Disruption in US-WEST-2 (Resolved)

What to do

• Check whether you use Braze in us, us-west-2. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-07-24 19:54 UTC and 2026-07-24 19:00 UTC may need a replay.

• Subscribe to Braze's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=braze works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Braze 1

1. resolvedJul 24, 2026, 7:00 PM UTC

   At approximately 7:30 AM ET, we became aware of an AWS networking outage in the US-WEST-2 region affecting network connectivity between 6:55 AM ET and 8:00 AM ET. AWS has since resolved the underlying issue. During the impact window, some customers may have experienced intermittent delays and latency in email delivery. Mail is now being delivered normally. As queue depth increased, some customers may have experienced residual delays in message delivery. These delays have been resolved as of 2:40 PM ET today. This disruption originated within AWS infrastructure and was not caused by any component of the Braze platform. For further details on the AWS incident, please refer to the AWS status page: https://health.aws.amazon.com/health/status

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.