Palo Alto Networks Outage History

Palo Alto Networks experienced degraded performance across multiple Cortex services (XDR, XSIAM, XSOAR8, XPANSE, and CLOUD) in the US/Americas region for 13.3 hours. The incident affected service performance and functionality for users in the affected region. A fix was implemented and monitored before the issue was fully resolved.

A Palo Alto Networks detector malfunctioned and incorrectly blocked customers from accessing legitimate hostnames and URLs due to false positive detections. The issue was resolved by disabling the problematic signature, and the root cause was identified and fixed within 5 minutes.

Palo Alto Networks experienced a delayed ingestion issue affecting Prisma Cloud's Americas US region (app3.prismacloud.io) for 4.5 hours. The incident was classified as minor and has been resolved.

Palo Alto Networks' edgeService (IoT) experienced a major service downgrade in the United States when it stopped fetching the latest verdicts from the backend service due to an upstream component issue. The incident lasted approximately 2 hours before being resolved. The company identified the root cause in the upstream service and monitored it until full resolution was achieved.

Palo Alto Networks' IoT Security service in the US experienced a 6.4-hour outage caused by a database issue that prevented customers from accessing the IoT portal. The technical team implemented a fix by stabilizing connection limits and restoring database functionality. All services were fully restored with verified data integrity and normal system operations.

Palo Alto Networks experienced delayed asset ingestion in Prisma Cloud affecting multiple regions including app2, app3, app4, app-eu, app-ind, app, and app2-eu. The issue was classified as minor and lasted 10.3 hours before being identified and resolved with an implemented fix.

Palo Alto Networks' Prisma Cloud experienced partial degraded performance for 16 hours on March 3, 2026. The issue was identified and a fix was implemented, with the service returning to normal operation. The incident was classified as minor with no specific user impact details provided.

A power outage in the AWS Middle East (Bahrain) region caused an outage affecting Palo Alto Networks' Cloud NGFW services in that region. Customers experienced failures when attempting to deploy new resources during the incident. The engineering team monitored AWS's recovery efforts and prepared to validate service health once the underlying infrastructure stabilized, with the incident lasting 6 minutes.

An intermittent network connectivity issue in Azure's Brazil South region caused disruptions to Palo Alto Networks' CNGFW services for 2 hours. Customers experienced intermittent service unavailability, degraded performance, and delays in monitoring and telemetry due to connectivity and packet loss issues. Azure mitigated the underlying network problem and the incident was resolved after monitoring confirmed service stability.

Palo Alto Networks' WildFire Global Cloud experienced an issue that caused delays in analysis report availability for customers. The incident lasted 7.8 hours, during which users experienced delayed access to their security analysis reports. The issue was identified and resolved with a fix implementation, followed by monitoring to ensure stability.