Palo Alto Networks Outage History

Palo Alto Networks degraded · 1 active incident View live status →

Palo Alto Networks had 89 outages in the last 2 years totaling 192h 12m of downtime — averaging 3.7 incidents per month.

There were 89 Palo Alto Networks outages since January 15, 2026 totaling 192h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.paloaltonetworks.com

Notice June 11, 2026

WildFire Taiwan Cloud Service Scheduled Maintenance

Detected by Pingoru
Jun 11, 2026, 09:14 PM UTC
Resolved
Jun 11, 2026, 10:23 PM UTC
Duration
1h 9m
Affected: WildFire Taiwan Cloud
Timeline · 2 updates
  1. scheduled Jun 11, 2026, 09:14 PM UTC

    We have a planned service maintenance for WildFire Taiwan Cloud on June 11, 2026 from 21:15:00 UTC to 22:15:00 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

  2. in progress Jun 11, 2026, 09:15 PM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Notice June 11, 2026

API Gateway is currently experiencing an issue.

Detected by Pingoru
Jun 11, 2026, 12:57 AM UTC
Resolved
Jun 11, 2026, 01:38 AM UTC
Duration
40m
Affected: Cloud Manager North America (United States)Cloud Manager North America (Canada)Cloud Manager Europe (United Kingdom)Cloud Manager APAC (Japan)Cloud Manager APAC (India)Cloud Manager APAC (Singapore)Cloud Manager Europe (Switzerland)Cloud Manager Europe (Germany)Cloud Manager APAC (Australia)Cloud Manager Middle East (Qatar)HubCloud Manager Europe (France)Cloud Manager APAC (Indonesia)Cloud Manager Middle East (Israel)Cloud Manager Middle East (Saudi Arabia)Cloud Manager Africa (South Africa)Cloud Manager North America (FedRamp Moderate)
Timeline · 2 updates
  1. investigating Jun 11, 2026, 12:57 AM UTC

    API Gateway is currently experiencing an issue . We are actively working on this issue and will provide another update by 3:00 AM UTC with further details.

  2. resolved Jun 11, 2026, 01:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 10, 2026

WildFire Europe Cloud Service Scheduled Maintenance

Detected by Pingoru
Jun 10, 2026, 03:25 PM UTC
Resolved
Jun 10, 2026, 04:32 PM UTC
Duration
1h 6m
Affected: WildFire Europe Cloud
Timeline · 2 updates
  1. scheduled Jun 10, 2026, 03:25 PM UTC

    We have a planned service maintenance for WildFire Europe Cloud on June 10, 2026 from 15:27 UTC to 16:27 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

  2. in progress Jun 10, 2026, 03:28 PM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Minor June 5, 2026

Enterprise DLP: US East Increased Latency and Error Rates

Detected by Pingoru
Jun 05, 2026, 05:38 PM UTC
Resolved
Jun 05, 2026, 05:38 PM UTC
Duration
—
Affected: DLP (NGFW) NAMPrisma Access DLP
Timeline · 1 update
  1. resolved Jun 05, 2026, 05:38 PM UTC

    Between 7:40am - 9:20am, Enterprise DLP in the US East region experienced increased latency and error rates for all traffic utilizing the EDM feature. The issue has been resolved and we are continuing to monitor the situation.

Read the full incident report →

Notice June 4, 2026

Prisma Cloud Application Security - Degraded

Detected by Pingoru
Jun 04, 2026, 10:26 PM UTC
Resolved
Jun 05, 2026, 01:32 AM UTC
Duration
3h 5m
Affected: Americas - US - app3.prismacloud.io
Timeline · 3 updates
  1. investigating Jun 04, 2026, 10:26 PM UTC

    We are currently investigating this issue.

  2. monitoring Jun 05, 2026, 12:46 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 05, 2026, 01:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 1, 2026

Cortex XSOAR - Degraded performance in the US region impacting some MSSP flows

Detected by Pingoru
Jun 01, 2026, 09:21 PM UTC
Resolved
Jun 02, 2026, 11:31 PM UTC
Duration
1d 2h
Affected: United States - Americas
Timeline · 4 updates
  1. investigating Jun 01, 2026, 09:21 PM UTC

    We are currently experiencing an issue with degraded performance impacting some MSSP flows. Customers may experience intermittent performance

  2. identified Jun 02, 2026, 01:35 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 02, 2026, 09:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 02, 2026, 11:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 1, 2026

WildFire Issue in Global Cloud

Detected by Pingoru
Jun 01, 2026, 03:36 AM UTC
Resolved
Jun 01, 2026, 03:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 01, 2026, 03:36 AM UTC

    Customers might experience intermittent failures when attempting to retrieve verdicts.

Read the full incident report →

Minor May 29, 2026

Service degradation in westus2 due to Azure cloud service issue

Detected by Pingoru
May 29, 2026, 08:26 AM UTC
Resolved
May 30, 2026, 03:49 AM UTC
Duration
19h 22m
Affected: westus2
Timeline · 4 updates
  1. investigating May 29, 2026, 08:26 AM UTC

    Azure is having service degradation impacting multiple services in the region westus2(https://azure.status.microsoft/en-us/status) We are continuously monitoring the status.

  2. identified May 29, 2026, 09:46 AM UTC

    Latest update from Azure: Mitigation efforts are underway to restore affected network components across dependent services, including Storage and Compute. Customers may begin to see signs of recovery as these actions progress

  3. identified May 29, 2026, 01:33 PM UTC

    Latest update from Azure: Recovered Azure services: Service Bus, Storage, App Service (Web Apps), Azure Site Recovery, Virtual Machine, Virtual Machine scale set, Backup (MAB), Azure Cosmos DB, Azure Log Analytics, Application Insights, Azure Monitor, Azure Resource Manager, Data Explorer, Azure IoT Hub, Microsoft Defender for Cloud Apps, Azure Container Registry, Azure Kubernetes Service, Azure Policy, Azure NetApp Files, Azure Resource Graph, Azure Synapse, Azure Database for MySQL - Flexible Server Mitigation efforts are still underway to restore affected network components across dependent services, including Storage and Compute

  4. resolved May 30, 2026, 03:49 AM UTC

    Azure team confirmed that this incident had been resolved.

Read the full incident report →

Minor May 21, 2026

Prisma Cloud Incident [APP] - Degraded

Detected by Pingoru
May 21, 2026, 09:04 PM UTC
Resolved
May 21, 2026, 10:44 PM UTC
Duration
1h 39m
Affected: Americas - US - app.prismacloud.io
Timeline · 4 updates
  1. investigating May 21, 2026, 09:04 PM UTC

    We are currently investigating this issue.

  2. identified May 21, 2026, 09:04 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 21, 2026, 10:01 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 21, 2026, 10:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 14, 2026

Cortex Gateway (GOV) is currently experiencing degraded availability affecting the GW login page. Existing active sessions are expected to remain operational.

Detected by Pingoru
May 14, 2026, 06:11 PM UTC
Resolved
May 14, 2026, 10:16 PM UTC
Duration
4h 5m
Affected: United States - GovernmentUnited States - GovermentUnited States - Government
Timeline · 4 updates
  1. investigating May 14, 2026, 06:11 PM UTC

    We are currently investigating this issue.

  2. identified May 14, 2026, 06:17 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 14, 2026, 08:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 14, 2026, 10:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 14, 2026

app4: Prisma cloud Page is not loading

Detected by Pingoru
May 14, 2026, 05:33 AM UTC
Resolved
May 14, 2026, 06:11 AM UTC
Duration
37m
Affected: Americas - US - app4.prismacloud.io
Timeline · 5 updates
  1. investigating May 14, 2026, 05:33 AM UTC

    We are currently investigating this issue.

  2. investigating May 14, 2026, 05:53 AM UTC

    We are continuing to investigate this issue.

  3. identified May 14, 2026, 06:00 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring May 14, 2026, 06:07 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved May 14, 2026, 06:11 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026

Prisma Cloud [App3] - Intermittent login failures

Detected by Pingoru
May 12, 2026, 06:53 PM UTC
Resolved
May 13, 2026, 05:20 PM UTC
Duration
22h 27m
Affected: Americas - US - app3.prismacloud.io
Timeline · 3 updates
  1. investigating May 12, 2026, 06:53 PM UTC

    We are currently investigating this issue.

  2. monitoring May 12, 2026, 07:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 13, 2026, 05:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026

Incident Notification: Azure Services Service Bus & API Management impacting CNGFW failing across South India & Australia Southeast multiple regions

Detected by Pingoru
May 11, 2026, 12:33 PM UTC
Resolved
May 11, 2026, 02:35 PM UTC
Duration
2h 1m
Affected: australiasoutheastsouthindia
Timeline · 2 updates
  1. investigating May 11, 2026, 12:33 PM UTC

    Azure Service Bus and Azure API Management in South India & Australia Southeast, may experience failures when managing resources and performing service operations. This includes issues such as creating, updating, or deleting resources, as well as intermittent timeouts when sending or receiving messages hosted in the affected regions. Current Status: Azure notified there might be an increase in timeout errors and connectivity issues impacting Service Bus, which is also affecting dependent Azure API Management workflows. Ongoing Actions: Our engineering team is working closely with the Azure team. You can also monitor the underlying platform status via the Azure Service Page. https://app.azure.com/h/0JLB-WKG/73b6c5

  2. resolved May 11, 2026, 02:35 PM UTC

    Azure has mitigated the incident. We are monitoring for continued stability.

Read the full incident report →

Minor May 6, 2026

Cortex XDR/XSIAM/XSOAR8/XPANSE/CLOUD - Degraded performance in the US region

Detected by Pingoru
May 06, 2026, 05:31 PM UTC
Resolved
May 06, 2026, 10:41 PM UTC
Duration
5h 9m
Affected: United States - AmericasUnited States - AmericasUnited States - AmericasUnited States - Americas
Timeline · 5 updates
  1. investigating May 06, 2026, 05:31 PM UTC

    We are currently investigating this issue.

  2. identified May 06, 2026, 06:10 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 06, 2026, 08:56 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring May 06, 2026, 09:52 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved May 06, 2026, 10:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 1, 2026

Prisma AIRS Product Degradation

Detected by Pingoru
May 01, 2026, 11:41 PM UTC
Resolved
May 02, 2026, 12:15 AM UTC
Duration
33m
Affected: AI Runtime Security APIAI Model SecurityAI Red Teaming
Timeline · 2 updates
  1. investigating May 01, 2026, 11:41 PM UTC

    We are currently investigating a service degradation affecting multiple Prisma AIRS products. Our engineering teams have been engaged and are actively working to identify the root cause and restore full service functionality.

  2. resolved May 02, 2026, 12:15 AM UTC

    The service degradation affecting multiple Prisma AIRS products has been resolved. All affected services have been restored to normal operation. Our teams will continue monitoring system health and performance to ensure stability.

Read the full incident report →

Notice April 30, 2026

WildFire Gov (FRH) Cloud Service Scheduled Maintenance

Detected by Pingoru
Apr 30, 2026, 11:31 PM UTC
Resolved
May 01, 2026, 12:41 AM UTC
Duration
1h 10m
Affected: WildFire AWF GovCloud(FRH)
Timeline · 2 updates
  1. scheduled Apr 30, 2026, 11:31 PM UTC

    We have a planned service maintenance for WildFire Gov (FRH) Cloud from April 30, 2026 23:40:00 UTC to May 01, 2026 00:40:00 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

  2. in progress Apr 30, 2026, 11:40 PM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Notice April 30, 2026

WildFire PubSec (FRM) Cloud Service Scheduled Maintenance

Detected by Pingoru
Apr 30, 2026, 06:38 PM UTC
Resolved
Apr 30, 2026, 08:01 PM UTC
Duration
1h 22m
Affected: WildFire AWF PubSec Cloud(FRM)
Timeline · 2 updates
  1. scheduled Apr 30, 2026, 06:38 PM UTC

    We have a planned service maintenance for WildFire PubSec (FRM) Cloud on April 30, 2026 from 19:00:00 UTC to 20:00:00 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

  2. in progress Apr 30, 2026, 07:00 PM UTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Minor April 30, 2026

AWS AP-NORTHEAST-1 outage impacting Cloud NGFW Services.

Detected by Pingoru
Apr 30, 2026, 10:35 AM UTC
Resolved
Apr 30, 2026, 12:37 PM UTC
Duration
2h 2m
Affected: Tokyo (ap-northeast-1)
Timeline · 3 updates
  1. investigating Apr 30, 2026, 10:35 AM UTC

    We have identified an issue with AWS affecting the Cloud NGFW AP-NORTHEAST-1 region. Customers may experience failures to deploy new resources.or delays in rule synchronization. Current Status: AWS is experiencing increased error rates and launch delays/errors for EC2 instances in AP-NORTHEAST-1 in the Tokyo region. This is primarily impacting instances EC2 launches resulting in launch failures. Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the AWS Health Dashboard. Next Update: 11:30 AM UTC 30th Apr 2026

  2. monitoring Apr 30, 2026, 11:29 AM UTC

    AWS has resolved the EC2 Availability. We are monitoring for continued stability.

  3. resolved Apr 30, 2026, 12:37 PM UTC

    AWS has resolved the issue.

Read the full incident report →

Minor April 27, 2026

AWS EU-WEST-3 outage impacting Cloud NGFW Services.

Detected by Pingoru
Apr 27, 2026, 11:50 AM UTC
Resolved
Apr 27, 2026, 08:59 PM UTC
Duration
9h 9m
Affected: Paris (eu-west-3)
Timeline · 3 updates
  1. investigating Apr 27, 2026, 11:50 AM UTC

    We have identified an issue with AWS affecting the Cloud NGFW EU-WEST-3 region. Customers may experience failures to deploy new resources or delays in rule synchronization Current Status: AWS is currently experiencing DynamoDB API error rate & EC2 Availability Issue Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the [Provider Name] Status Page: [Link]. Next Update: 1 PM UTC 27th Apr 2026

  2. monitoring Apr 27, 2026, 12:30 PM UTC

    AWS has resolved the Lambda, EC2 Availability & Dynamo DB errors. We are monitoring for continued stability.

  3. resolved Apr 27, 2026, 08:59 PM UTC

    AWS has closed the issues and Cloud NGFW services are no longer impacted

Read the full incident report →

Minor April 24, 2026

[Azure] [EastUS] outage impacting Cloud NGFW Services

Detected by Pingoru
Apr 24, 2026, 06:54 PM UTC
Resolved
Apr 25, 2026, 01:21 AM UTC
Duration
6h 27m
Affected: eastus
Timeline · 3 updates
  1. investigating Apr 24, 2026, 06:54 PM UTC

    We have identified an issue with Azure affecting the Cloud NGFW EastUS region. Customers may experience failures to deploy new resources Current Status: Azure is currently experiencing failures or delays when provisioning, scaling, or updating Azure resources. This is impacting our ability to Provision New firewalls and perform autoscale actions Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the Azure Status Page: https://azure.status.microsoft/en-us/status Next Update: in 4 hours 22:54:00 UTC 4/24/26

  2. investigating Apr 24, 2026, 11:05 PM UTC

    We have identified an issue with Azure affecting the Cloud NGFW EastUS region. Customers may experience failures to deploy new resources Current Status: Azure is still experiencing failures or delays when provisioning, scaling, or updating Azure resources. This is impacting our ability to Provision New firewalls and perform autoscale actions Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. You can also monitor the underlying platform status via the Azure Status Page: https://azure.status.microsoft/en-us/status Next Update: in 4 hours 03:04:54 UTC UTC 4/25/26

  3. resolved Apr 25, 2026, 01:21 AM UTC

    The Azure East US infrastructure issue has been resolved by Microsoft. Cloud NGFW for Azure - eastus is fully operational. No active Azure CSP provider incidents remain. Customers should no longer experience failures when provisioning, scaling, or updating resources.

Read the full incident report →