Skip to content

Incident detail

AWS us-east-1 outage impacting Cloud NGFW Services

Resolved incidentMinor

Timeline window

to

Get alerted the next time Palo Alto Networks breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Palo Alto Networks posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    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.

  2. Investigating

    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.

  3. Resolved

    This incident has been resolved.

Keep exploring

More from Palo Alto Networks

Neighboring incidents on Palo Alto Networks's timeline and the rest of their record on OutageDeck.