Palo Alto Networks Outage History

Palo Alto Networks' Cortex Gateway (GOV) experienced degraded availability for 4.1 hours, specifically affecting the login page for Federal components while existing active sessions remained operational. The issue was identified and a fix was implemented, with the incident being resolved after a monitoring period.

The Palo Alto Networks Prisma Cloud service experienced a major incident where the app4.prismacloud.io page was not loading for users in the Americas - US region. The issue affected the primary application interface, preventing users from accessing the Prisma Cloud platform. The incident was resolved after 40 minutes once engineers identified the root cause and implemented a fix.

Palo Alto Networks' Prisma Cloud experienced intermittent login failures affecting the Americas US region (app3.prismacloud.io) for approximately 22.6 hours. The issue prevented users from reliably accessing the platform during this period. A fix was implemented and monitored before the incident was fully resolved.

Azure Service Bus and API Management failures in South India and Australia Southeast regions caused Palo Alto Networks CNGFW services to fail, with users experiencing timeout errors and connectivity issues when creating, updating, or deleting resources. The incident lasted 2.1 hours and affected message sending/receiving operations as well as dependent API Management workflows. Azure mitigated the underlying platform issues and the service was restored with continued monitoring for stability.

Palo Alto Networks' Prisma Cloud experienced intermittent login failures affecting the Americas US region (app3.prismacloud.io) for 1.7 hours. The issue was identified and a fix was implemented, with the service returning to normal operation. The incident was resolved after a monitoring period to ensure stability.

An AWS cooling system failure in availability zone use1-az4 in the US-EAST-1 region caused elevated error rates and latencies for Palo Alto Networks Cloud NGFW services for 22.6 hours. The incident affected EC2 instances and EBS volumes in the impacted zone, with AWS shifting traffic away from the affected zone and recommending customers use other availability zones in the region. The incident was resolved after AWS restored normal temperatures and cooling systems in the affected zone.

Palo Alto Networks experienced degraded performance across multiple Cortex services (XDR, XSIAM, XSOAR8, XPANSE, and CLOUD) in the US/Americas region for 5.2 hours. The issue was identified and a fix was implemented, with the incident fully resolved after a monitoring period.

Palo Alto Networks experienced a service degradation affecting multiple Prisma AIRS products for 39 minutes. Engineering teams investigated the issue and worked to identify the root cause. All affected services were restored to normal operation with continued monitoring for system stability.

An AWS outage in the AP-NORTHEAST-1 (Tokyo) region caused EC2 instance launch failures and increased error rates, impacting Palo Alto Networks Cloud NGFW services. Customers experienced failures when deploying new resources and delays in rule synchronization for approximately 2.1 hours. The issue was resolved when AWS restored EC2 availability in the affected region.

An Azure datacenter event in the France Central region caused disruptions to Storage and Cosmos DB services, which impacted Palo Alto Networks Cloud NGFW services for 8.3 hours. Customers experienced intermittent service unavailability, degraded performance, delays in monitoring and telemetry, along with higher than expected latency, timeouts, and HTTP 500 errors. The issue was resolved after Azure mitigated the underlying infrastructure problems and restored affected services.