Palo Alto Networks Outage History

Palo Alto Networks' Cortex XSOAR experienced degraded performance in the US region for 26.2 hours, specifically impacting some MSSP (Managed Security Service Provider) flows with intermittent performance issues. The incident was identified, a fix was implemented and monitored, and the service was fully restored.

Palo Alto Networks' WildFire Global Cloud experienced a 33.2-hour outage caused by unexpected traffic that was 8 times higher than normal, overwhelming the service's autoscaling capacity. Users encountered errors while attempting to get verdicts from the threat analysis service. The issue was resolved after engineers identified the root cause and implemented a fix to handle the increased traffic load.

Palo Alto Networks experienced service degradation in the westus2 region for 19.4 hours due to an Azure cloud service issue affecting multiple Azure services including Storage, Compute, Virtual Machines, and other dependent network components. The incident was resolved when Azure's mitigation efforts successfully restored the affected network infrastructure and services. Palo Alto Networks monitored the situation throughout the incident and confirmed resolution once Azure restored their services.

Palo Alto Networks experienced a degraded service incident affecting the Prisma Cloud application (app.prismacloud.io) in the Americas US region for 1.7 hours. The issue was identified and a fix was implemented, with the service being monitored before full resolution. The incident was resolved after the implemented fix successfully restored normal service operations.

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.