Palo Alto Networks Outage History

Started Jul 16, 2026, 11:06 AM UTC· resolved Jul 16, 2026, 07:12 PM UTC

1. investigating Jul 16, 2026, 11:06 AM UTC

   We are currently investigating increased error rates and latency in multiple regions.

2. investigating Jul 16, 2026, 11:18 AM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 16, 2026, 11:57 AM UTC

   We have deployed a fix and are seeing functionality begin to return to normal. We will continue to monitor the situation and will confirm once things have fully resolved.

4. monitoring Jul 16, 2026, 12:54 PM UTC

   We are still seeing some intermittent issues in multiple regions, but error rates have dropped significantly. We are working to alleviate these intermittent issues now.

5. monitoring Jul 16, 2026, 01:57 PM UTC

   We are seeing full recovery in all regions now. We will continue to monitor for a few hours before resolving the incident.

6. resolved Jul 16, 2026, 07:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 10, 2026, 05:58 AM UTC· resolved Jul 10, 2026, 01:37 PM UTC

1. investigating Jul 10, 2026, 05:58 AM UTC

   We are currently investigating this issue.

2. identified Jul 10, 2026, 07:19 AM UTC

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

3. monitoring Jul 10, 2026, 07:24 AM UTC

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

4. monitoring Jul 10, 2026, 07:27 AM UTC

   We have applied a fix and are currently monitoring the system.

5. monitoring Jul 10, 2026, 10:05 AM UTC

   We are still monitoring and waiting for the system to catch up.

6. monitoring Jul 10, 2026, 01:09 PM UTC

   We are continuing to monitor the system as it catches up on the lag.

7. monitoring Jul 10, 2026, 01:10 PM UTC

   We are continuing to monitor the system as it catches up on the lag.

8. resolved Jul 10, 2026, 01:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 07, 2026, 07:36 PM UTC· resolved Jul 08, 2026, 12:00 AM UTC

1. investigating Jul 07, 2026, 07:36 PM UTC

   We are currently investigating this issue.

2. identified Jul 07, 2026, 08:07 PM UTC

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

3. monitoring Jul 07, 2026, 09:30 PM UTC

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

4. resolved Jul 08, 2026, 12:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 07, 2026, 06:06 PM UTC· resolved Sep 24, 2026, 02:29 AM UTC

1. monitoring Jul 07, 2026, 06:06 PM UTC

   We have identified an issue with Azure affecting the Cloud NGFW westeurope and southcentralus regions. Customers may experience failures to during autoscaling and during deployment of new resources. Current Status: Azure is currently experiencing compute capacity issues within the regions. This is impacting our ability to scale out new virtual machines. Ongoing Actions: Our engineering team is monitoring the provider’s recovery efforts and is prepared to validate service health as soon as infrastructure stabilizes. Next Update: Wednesday, July 8th, 17:00UTC

2. monitoring Jul 08, 2026, 03:45 PM UTC

   Azure is still working on recovery. We are continuously monitoring their progress.

3. monitoring Jul 10, 2026, 09:16 AM UTC

   Azure is still working on recovery. We are continuously monitoring their progress.

4. monitoring Jul 12, 2026, 04:49 AM UTC

   We are continuing to monitor for any further issues.

5. monitoring Jul 12, 2026, 04:53 AM UTC

   Azure is still working on recovery. We are continuously monitoring their progress. Next Update: July 13th, 8:00UTC

6. monitoring Jul 12, 2026, 04:53 AM UTC

   Azure is still working on recovery. We are continuously monitoring their progress. Next Update: July 13th, 8:00UTC

7. monitoring Jul 15, 2026, 03:12 PM UTC

   Update - Azure is still working on recovery. We are continuously monitoring their progress. Next Update: July 16th, 8:00UTC

8. monitoring Jul 17, 2026, 12:10 PM UTC

   Azure is still working on recovery. We are continuously monitoring their progress. Next Update: July 20th, 8:00UTC

9. monitoring Jul 22, 2026, 05:05 AM UTC

   Azure is still working on recovery. We are continuously monitoring their progress. Next Update: July 23th, 8:00UTC

10. monitoring Jul 23, 2026, 08:00 PM UTC

    We are impacted by a capacity issue within Azure data centers affecting Cloud NGFW in the West Europe and South Central US regions. Customers may experience failures during autoscaling, panorama migrations, migrations to premium instances, software updates or the deployment of new resources. Until the capacity issue is resolved by Microsoft: - Maintain Steady-State: Keep current resource configurations intact and postpone premium SKU migrations or panorama migrations. - Normalize Traffic: Maintain your current traffic baselines where possible to avoid triggering sudden autoscaling needs. - Defer New Deployments: Hold off on launching new resources until full capacity is restored.

11. monitoring Jul 27, 2026, 07:02 PM UTC

    We are continuing to monitor for any further issues.

12. monitoring Aug 03, 2026, 07:05 AM UTC

    Azure is still working on recovery. We are continuously monitoring their progress.

13. monitoring Sep 16, 2026, 03:19 PM UTC

    Creation of new firewall instances has been restored in the West Europe and South Central US regions. Customers can now deploy new Cloud NGFW resources as normal. We are continuing to work with Azure and monitor capacity to resolve remaining impacts affecting autoscaling, migrations, and software updates.

14. resolved Sep 24, 2026, 02:29 AM UTC

    Availability issues are now resolved

Read the full incident report →

Started Jul 02, 2026, 10:00 AM UTC· resolved Jul 02, 2026, 05:55 PM UTC

1. investigating Jul 02, 2026, 10:00 AM UTC

   We are currently investigating this issue.

2. identified Jul 02, 2026, 11:22 AM UTC

   We have identified the issue and actively working on a solution.

3. identified Jul 02, 2026, 01:12 PM UTC

   We have applied a mitigation and currently monitoring the progress.

4. identified Jul 02, 2026, 05:09 PM UTC

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

5. monitoring Jul 02, 2026, 05:16 PM UTC

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

6. resolved Jul 02, 2026, 05:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2026, 06:49 PM UTC· resolved Jul 01, 2026, 11:30 PM UTC

1. scheduled Jul 01, 2026, 06:49 PM UTC

   We have a planned service maintenance for WildFire Us Cloud on July 01, 2026 from 21:30:00 UTC to 23:30:00 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

2. scheduled Jul 01, 2026, 08:30 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress Jul 01, 2026, 09:30 PM UTC

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

Read the full incident report →

Started Jun 30, 2026, 09:30 PM UTC· resolved Jun 30, 2026, 10:04 PM UTC

1. identified Jun 30, 2026, 09:30 PM UTC

   We are aware of an ongoing AWS operational issue in the EU-NORTH-1 (Stockholm) region affecting EC2 APIs and Elastic Load Balancing. This is impacting provisioning and management operations for Cloud NGFW resources in EU-NORTH-1. Existing Cloud NGFW instances and traffic processing are not affected — the impact is limited to new instance launches and API-driven operations in this region. We are monitoring AWS's progress and will update as we learn more.

2. resolved Jun 30, 2026, 10:04 PM UTC

   The issue has been resolved and all services are operating normally.

Read the full incident report →

Started Jun 30, 2026, 01:52 PM UTC· resolved Jun 30, 2026, 03:15 PM UTC

1. investigating Jun 30, 2026, 01:52 PM UTC

   We are currently investigating this issue.

2. resolved Jun 30, 2026, 03:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 12:57 PM UTC· resolved Jun 29, 2026, 03:06 PM UTC

1. investigating Jun 29, 2026, 12:57 PM UTC

   We are currently investigating this issue.

2. identified Jun 29, 2026, 01:10 PM UTC

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

3. monitoring Jun 29, 2026, 02:38 PM UTC

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

4. resolved Jun 29, 2026, 03:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 25, 2026, 09:33 AM UTC· resolved Jun 25, 2026, 11:18 AM UTC

1. identified Jun 25, 2026, 09:33 AM UTC

   We have identified a service disruption affecting Cloud NGFW. Customers may experience degraded performance or connectivity. Current Status: An issue within the Data Plane has triggered a degraded service interruption. Our team has initiated a high-priority incident response to restore normal traffic flow as quickly as possible. Ongoing Actions: We are currently working on the resolution. Next Update: 21:30 UTC 25th Jun 2026

2. resolved Jun 25, 2026, 11:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2026, 03:02 PM UTC· resolved Jun 18, 2026, 11:38 PM UTC

1. investigating Jun 18, 2026, 03:02 PM UTC

   Alerts are delayed in app2.eu stack, we are investigating.

2. identified Jun 18, 2026, 07:46 PM UTC

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

3. identified Jun 18, 2026, 08:53 PM UTC

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

4. identified Jun 18, 2026, 10:16 PM UTC

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

5. monitoring Jun 18, 2026, 10:30 PM UTC

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

6. resolved Jun 18, 2026, 11:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 16, 2026, 04:41 PM UTC· resolved Jun 16, 2026, 05:12 PM UTC

1. investigating Jun 16, 2026, 04:41 PM UTC

   We are currently experiencing issues with Cortex XDR/XSIAM – EU region. We are actively working on this and will post continuous updates on the issue. The current impact is that agents in EU region are having sporadic connectivity issues to Cortex XDR. All agent side protection is still active as well as the UI connectivity

2. resolved Jun 16, 2026, 05:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2026, 11:27 PM UTC· resolved Jun 12, 2026, 12:38 AM UTC

1. scheduled Jun 11, 2026, 11:27 PM UTC

   We have a planned service maintenance for WildFire Eu Cloud from June 11, 2026 23:30:00 UTC to June 12, 2026 00:30:00 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

2. in progress Jun 11, 2026, 11:30 PM UTC

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

Read the full incident report →

Started Jun 11, 2026, 12:57 AM UTC· resolved Jun 11, 2026, 01:38 AM UTC

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 →

Started Jun 05, 2026, 05:38 PM UTC· resolved Jun 05, 2026, 05:38 PM UTC

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 →

Started Jun 04, 2026, 10:26 PM UTC· resolved Jun 05, 2026, 01:32 AM UTC

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 →

Started Jun 01, 2026, 09:21 PM UTC· resolved Jun 02, 2026, 11:31 PM UTC

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 →

Started Jun 01, 2026, 03:00 AM UTC· resolved Jun 01, 2026, 03:00 AM UTC

1. resolved Jun 01, 2026, 03:36 AM UTC

   Customers might experience intermittent failures when attempting to retrieve verdicts.

Read the full incident report →

Started May 29, 2026, 08:26 AM UTC· resolved May 30, 2026, 03:49 AM UTC

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 →

Started May 21, 2026, 09:04 PM UTC· resolved May 21, 2026, 10:44 PM UTC

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 →

Started May 20, 2026, 08:30 AM UTC· resolved May 22, 2026, 09:30 PM UTC

1. resolved May 23, 2026, 01:05 AM UTC

   Issue Description On May 21, 2026, customers reported their traffic being blocked due to TID 97011: “D-Link Router DHCP Hostname Command Injection Vulnerability”, the TID was designed to block OS Command Injection attempts within the hostname fields of DHCP requests. However, the signature included a broad command-matching filter that led to false positives across customer environments, as it incorrectly triggered on legitimate hostnames containing overlapping character strings. Findings and Technical Analysis The D-Link Router DHCP Hostname Command Injection Vulnerability (TID 97011) is an OS command injection flaw that allows command execution attempts through the DHCP Hostname fields. This vulnerability has coverage related to CVE-2025-69542 and CVE-2025-14659, such as the DIR-895LA1 which targets D-Link devices and DIR-860LB1, respectively. Previous Detection Logic The initial detection logic for TID 97011 included a command-filtering string within DHCP hostname fields that lacked strict boundary delimiters Root Cause The false positive (FP) occurred because the signature's command-validation logic triggered against legitimate hostnames containing the targeted command string as a substring. This broad matching behavior resulted in unintended traffic disruptions for multiple customers. Proposed Solutions & Mitigation We improved the signature logic to make it more resilient against false positives. The updated signature has been released with content 9105-10068.

Read the full incident report →

Started May 18, 2026, 08:00 AM UTC· resolved May 18, 2026, 08:50 AM UTC

1. resolved May 26, 2026, 10:00 PM UTC

   We have experienced a sporadic issue impacting EDR data uploads in the US region. Cortex XDR agent local protection continues to function normally.

Read the full incident report →

Started May 14, 2026, 05:33 AM UTC· resolved May 14, 2026, 06:11 AM UTC

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 →

Started May 12, 2026, 06:53 PM UTC· resolved May 13, 2026, 05:20 PM UTC

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 →

Started May 11, 2026, 12:33 PM UTC· resolved May 11, 2026, 02:35 PM UTC

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 →