Palo Alto Networks incident
AWS us-east-1 outage impacting Cloud NGFW Services
Palo Alto Networks experienced a minor incident on May 8, 2026 affecting N.Virginia (us-east-1), lasting 22h 30m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 04:08 AM UTC
we have identified an issue with AWS affecting the Cloud NGFW which is due to AWS Operational issue - Amazon Elastic Compute Cloud (N. Virginia) Availability Zone (use1-az4) in the US-EAST-1 Region CSP Health Status: https://health.aws.amazon.com/health/status AWS team are actively working to restore temperatures to normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region, though progress is slower than originally anticipated. Since our last update we have made incremental progress to restore cooling systems within the affected AZ, which will not be visible to external customers but are required for the restoration of affected services. In the impacted Availability Zone, EC2 Instances, EBS Volumes, and other AWS Services are also experiencing elevated error rates and latencies for some workflows. As part of our recovery effort, we have shifted traffic away from the impacted Availability Zone for most services. We recommend customers utilize one of the other Availability Zones in the US-EAST-1 Region, as existing instances in other AZs remain unaffected by this issue. If immediate recovery is required, we recommend customers restore from EBS Snapshots and/or replace affected resources by launching new replacement resources in one of the unaffected zones. We will provide an update by 10:00 PM PDT, or sooner if we have additional information to share.
- investigating May 08, 2026, 10:10 AM UTC
AWS continues to experience the Operational issues with EC2 & EBS Volumes. You can also monitor the underlying platform status via the AWS Health Status https://health.aws.amazon.com/health/status.
- resolved May 09, 2026, 02:38 AM UTC
This incident has been resolved.