Palo Alto Networks

Affected: WildFire Germany Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 11:28 UTC

   WildFire is currently experiencing an issue in Germany Cloud. We are actively working on this issue and will provide another update by 13:30 UTC with further details. Customer Impact: Frequent disconnection and Delay in Sample processing Workaround: N/A

2. identified 2026-10-20 12:20 UTC

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

3. monitoring 2026-10-20 12:22 UTC

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

4. resolved 2026-10-20 12:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United Kingdom, United Kindom, United Kingdom, United Kingdom, United Kingdom

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-20 07:52 UTC

   We are currently experiencing degraded performance in the UK region. We have identified the root cause and are implementing a fix.

2. identified 2026-10-20 10:30 UTC

   The issue originates with our cloud vendor, and we are continuing to work closely with them to mitigate its impact.

3. identified 2026-10-20 11:50 UTC

   We are seeing gradual improvements in some areas of the UK region and are continuing to work closely with our cloud vendor to mitigate the issue

4. identified 2026-10-20 14:17 UTC

   We continue to see gradual improvement in the situation and are closely monitoring the status

5. monitoring 2026-10-20 16:06 UTC

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

6. resolved 2026-10-21 01:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire UK Cloud

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple services are experiencing issues in the europe-west2 region..

1. investigating 2026-10-20 06:52 UTC

   WildFire is currently experiencing an issue in UK Cloud. We are actively working on this issue and will provide another update by 9:00 AM UTC with further details. Customer Impact: Delay in sample processing and client disconnection errors Workaround: N/A

2. investigating 2026-10-20 07:37 UTC

   This is due to an outage from GCP.

3. investigating 2026-10-20 09:46 UTC

   GCP is still continuing investigating the issue. There is no ETA yet.

4. investigating 2026-10-20 13:08 UTC

   GCP is still continuing investigating the issue -https://status.cloud.google.com/regional/europe#status-table

5. investigating 2026-10-20 15:24 UTC

   As per GCP most of their services are up in europe-west2 region. But we still see some n/w failures. We are following up with GCP.

6. identified 2026-10-20 16:06 UTC

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

7. monitoring 2026-10-20 16:10 UTC

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

8. resolved 2026-10-20 16:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Americas

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 00:51 UTC

   We are currently investigating this issue with URL Filtering Detection Service, that affects detection features offered by AI Runtime Security API. Customer Impact: Scan requests are still being processed and return successful responses, and all other detections work as normal....

2. resolved 2026-10-15 01:26 UTC

   The issue affecting the URL Filtering Detection Service in AI Runtime Security API has been resolved. URL filtering detection features has worked normally since 01:07 UTC. Customer Impact: From about 00:00 UTC to 01:07 UTC on October 15, 2026, URL content in prompts and...

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: N.Virginia (us-east-1)

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-10-09 20:33 UTC

   We are investigating reports of "Access Denied" errors when accessing the Cloud NGFW for AWS management portal. Multiple customers are affected. Firewall traffic processing is not impacted - this issue is limited to portal access. We will provide an update within 30 minutes.

2. resolved 2026-10-09 20:55 UTC

   Message: This incident has been resolved. Access to the Cloud NGFW for AWS management portal is fully restored. Beginning at approximately 18:05 UTC, a configuration change applied during a routine internal deployment caused the portal's content delivery layer to lose access to...

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire Singapore Cloud, WildFire UK Cloud, WildFire Germany Cloud, WildFire India Cloud, WildFire Switzerland Cloud, WildFire Indonesia Cloud, WildFire Taiwan Cloud, WildFire France Cloud, WildFire Qatar Cloud, WildFire South Korea Cloud, WildFire Israel Cloud, WildFire Saudi Arabia Cloud, Wildfire Spain Cloud, WildFire EU Regulated Cloud

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 23:56 UTC

   WildFire is currently experiencing an issue in UK/Taiwan/South Korea/Switzerland/Spain/Singapore/Saudi Arabia/Qatar/Israel/Indonesia/India/Germany/France/EU Regulated Cloud. We are actively working on this issue and will provide another update by with further details. Customer...

2. identified 2026-10-08 01:13 UTC

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

3. identified 2026-10-08 01:31 UTC

   Singapore/UK/Israel/Spain Clouds are operational

4. identified 2026-10-08 01:41 UTC

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

5. identified 2026-10-08 01:44 UTC

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

6. identified 2026-10-08 01:58 UTC

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

7. monitoring 2026-10-08 02:04 UTC

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

8. resolved 2026-10-08 02:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Customer Support Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-06 22:17 UTC

   We are observing an intermittent availability issue with multiple customer-facing services. The operations team is investigating the problem.

2. monitoring 2026-10-06 23:20 UTC

   The Customer Support portal availability issue has been resolved. The operations team is monitoring service availability.

3. resolved 2026-10-07 00:40 UTC

   No issues were observed during the 1-hour observation period. No further updates are expected on this thread.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Americas - US - app3.prismacloud.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-29 06:32 UTC

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

2. identified 2026-09-29 09:36 UTC

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

3. identified 2026-09-29 13:55 UTC

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

4. identified 2026-09-29 15:35 UTC

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

5. identified 2026-09-29 17:29 UTC

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

6. identified 2026-09-29 18:28 UTC

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

7. identified 2026-09-29 19:40 UTC

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

8. identified 2026-09-29 20:47 UTC

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

9. identified 2026-09-29 21:43 UTC

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

10. identified 2026-09-29 22:35 UTC

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

11. identified 2026-09-29 23:55 UTC

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

12. identified 2026-09-30 00:59 UTC

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

13. identified 2026-09-30 02:01 UTC

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

14. identified 2026-09-30 07:50 UTC

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

15. identified 2026-09-30 09:44 UTC

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

16. identified 2026-09-30 14:00 UTC

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

17. identified 2026-09-30 16:16 UTC

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

18. identified 2026-09-30 17:33 UTC

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

19. identified 2026-09-30 18:42 UTC

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

20. identified 2026-09-30 20:11 UTC

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

21. identified 2026-09-30 21:29 UTC

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

22. identified 2026-09-30 22:41 UTC

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

23. identified 2026-10-01 00:14 UTC

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

24. identified 2026-10-01 01:40 UTC

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

25. identified 2026-10-01 02:37 UTC

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

26. resolved 2026-10-01 05:25 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: APAC - Taiwan, EMEA - Netherlands, Americas - US West, Americas - US Central

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 19:01 UTC

   We are currently investigate the issue.

2. resolved 2026-09-02 22:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Americas - US Central

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 17:00 UTC

   We are monitoring the system and we will provide another update by 12pm PDT with further details. Customer Impact: Customer will experience service degradation Workaround: "N/A"

2. monitoring 2026-09-01 17:02 UTC

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

3. resolved 2026-09-01 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Cortex Gateway

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 15:24 UTC

   We are currently investigating this issue.

2. monitoring 2026-09-01 15:34 UTC

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

3. resolved 2026-09-02 02:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Americas, United States - Americas

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 17:47 UTC

   We are currently investigating this issue.

2. investigating 2026-08-26 18:05 UTC

   We are experiencing degraded XSOAR/XSIAM performance in the US region with automation executions

3. investigating 2026-08-26 18:37 UTC

   We are continuing to investigate this issue.

4. identified 2026-08-26 20:39 UTC

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

5. monitoring 2026-08-26 20:50 UTC

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

6. resolved 2026-08-26 21:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire India Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 18:24 UTC

   WildFire is currently experiencing an issue in the India Cloud. We are actively working on this issue and will provide another update by 20:00 UTC with further details. Customer Impact: Delay of sample processing and verdict availability Workaround: N/A

2. identified 2026-08-25 18:50 UTC

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

3. monitoring 2026-08-25 18:53 UTC

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

4. resolved 2026-08-25 18:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire India Cloud

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 17:26 UTC

   WildFire is currently experiencing an issue in India Cloud. We are actively working on this issue and will provide another update by 19:00 UTC with further details. Customer Impact: Delay of sample processing and intermittent failure of quering. Workaround: N/A

2. identified 2026-08-24 17:57 UTC

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

3. monitoring 2026-08-24 18:05 UTC

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

4. resolved 2026-08-24 18:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Americas, United States - Americas, United States - Americas

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-21 20:24 UTC

   We are experiencing sporadic third-party log collection performance on a small subset of tenants in the US region, affecting log collection from third-party vendors through our native third-party collectors. Marketplace integrations are not affected

2. identified 2026-08-22 06:10 UTC

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

3. monitoring 2026-08-22 18:41 UTC

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

4. resolved 2026-08-25 01:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Americas

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region..

1. identified 2026-08-20 18:16 UTC

   We are observing some increased latency in the US West region due to the ongoing GCP outage (link below). Overall health of the region is within acceptable bounds. GCP Outage link: https://status.cloud.google.com/regional/americas#status-table

2. monitoring 2026-08-20 18:33 UTC

   GCP is seeing recovery for affected products. We will continue monitoring the situation.

3. resolved 2026-08-20 19:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-08-19 22:59 UTC

   Incident Overview The Device Security Cloud Service is currently experiencing downstream impact due to degradation of the SLS (Security Logging Service) log forwarding and streaming service. Core device security enforcement remains fully functional, but log ingestion and...

2. investigating 2026-08-19 23:10 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-08-20 00:54 UTC

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

4. monitoring 2026-08-20 00:54 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-08-21 18:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: N.Virginia (us-east-1)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-19 15:10 UTC

   We are investigating login service degradation on the Cloud NGFW Management Console. Note: Data plane traffic and security enforcement are not impacted by this event. Current Status: Engineers are currently investigating the issue. Next Update: 06:00 PM UTC, 19th Aug 2026

2. monitoring 2026-08-19 17:35 UTC

   Service Degradation has been mitigated. We will continue to monitor service health.

3. monitoring 2026-08-19 17:36 UTC

   Service Degradation has been mitigated. We will continue to monitor service health. Next Update: 08:00 PM UTC, 19th Aug 2026

4. monitoring 2026-08-19 22:02 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-08-19 22:02 UTC

   The login service degradation on the Cloud NGFW Management Console has been fully resolved. All services are operating normally.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Canada, Canada, Canada, Canada

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-17 21:31 UTC

   We are experiencing degraded performance in the CA region. Cortex XDR agent local protection continues to function normally.

2. identified 2026-08-17 22:12 UTC

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

3. monitoring 2026-08-18 00:52 UTC

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

4. resolved 2026-08-18 04:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-11 19:00 UTC

   We experienced degraded performance in the US region Cortex XDR agent local protection continues to function normally.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire Global Cloud, WildFire Europe Cloud, WildFire Singapore Cloud, WildFire Japan Cloud, WildFire UK Cloud, WildFire U.S. Government Cloud, WildFire Canada Cloud, WildFire Australia Cloud, WildFire Germany Cloud, WildFire India Cloud, WildFire Switzerland Cloud, WildFire Poland Cloud, WildFire Indonesia Cloud, WildFire Taiwan Cloud, WildFire France Cloud, WildFire Qatar Cloud, WildFire South Korea Cloud, WildFire Israel Cloud, WildFire Saudi Arabia Cloud, WildFire Italy Cloud, Wildfire Spain Cloud, WildFire AWF PubSec Cloud(FRM), WildFire AWF GovCloud(FRH), WildFire South Africa Cloud, WildFire EU Regulated Cloud, WildFire GVS Cloud, WildFire US Native Cloud, WildFire Delhi Cloud, WildFire Brazil Cloud, WildFire Finland Cloud, WildFire EU Sovereign Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-11 11:06 UTC

   WildFire is currently experiencing an issue in the regional Clouds. We are actively working on this issue and will provide another update by with 1:00 PM UTC for frther details. Customer Impact: Service degradation. Workaround: NA

2. identified 2026-08-11 12:08 UTC

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

3. monitoring 2026-08-11 12:09 UTC

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

4. resolved 2026-08-11 12:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Americas - US - app3.prismacloud.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-07 06:55 UTC

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

2. monitoring 2026-08-07 07:09 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2026-08-07 10:48 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-08-07 17:19 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-08-08 07:23 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2026-08-09 13:16 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2026-08-10 06:10 UTC

   We are continuing to monitor for any further issues.

8. monitoring 2026-08-10 18:15 UTC

   We are continuing to monitor for any further issues.

9. monitoring 2026-08-11 10:37 UTC

   We are continuing to monitor for any further issues.

10. monitoring 2026-08-11 23:46 UTC

    We are continuing to monitor for any further issues.

11. monitoring 2026-08-12 15:30 UTC

    We are continuing to monitor for any further issues.

12. monitoring 2026-08-13 20:56 UTC

    We are continuing to monitor for any further issues.

13. monitoring 2026-08-14 17:43 UTC

    We are continuing to monitor for any further issues.

14. resolved 2026-08-24 03:07 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Customer Support Portal

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-02 00:29 UTC

   Customer Service Portal will be going through an unplanned emergency change management to address an issue which impacts the infrastructure. Customers may face intermittent login issues and license activation failures from 8.2.26 12:00a to 8.2.26 at 3:30a UTC.

2. resolved 2026-08-02 03:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: australiaeast, australiasoutheast, canadacentral, centralus, eastasia, eastus, eastus2, northeurope, uksouth, ukwest, westeurope, westus, westus2, westus3, brazilsouth, japaneast, northcentralus, southeastasia, canadaeast, centralindia, francecentral, germanywestcentral, israelcentral, italynorth, japanwest, koreacentral, mexicocentral, newzealandnorth, norwayeast, southafricanorth, southcentralus, southindia, spaincentral, swedencentral, switzerlandnorth, switzerlandwest, uaenorth, westcentralus

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-08-01 00:25 UTC

   Customers using Panorama to manage their Azure Cloud Native Next-Generation Firewall (CNGFW) environment may experience errors when creating or updating firewalls and services, or when utilizing logging services. We have identified the issue and are actively working on a fix....

2. resolved 2026-08-02 06:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Customer Support Portal

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 03:35 UTC

   Incident management team is actively working the issue.

2. investigating 2026-07-30 04:43 UTC

   Issue was identified as NAT pool exhaustion on the firewall due to heavy traffic from a single IP. This has been remediated and services are partially restored. Incident team continuing to monitor.

3. investigating 2026-07-30 17:16 UTC

   This issue has been resolved and the Customer Support Portal if fully operational.

4. investigating 2026-07-30 17:29 UTC

   RCA in progress.

5. resolved 2026-07-30 17:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 06:44 UTC

   We are currently investigating this issue.

2. identified 2026-07-17 07:28 UTC

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

3. monitoring 2026-07-17 08:58 UTC

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

4. resolved 2026-07-17 10:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: APAC (Mumbai) - Prisma SaaS, APAC (Singapore) - Prisma SaaS, APAC (Tokyo) - Prisma Access, EMEA (Frankfurt) - Prisma SaaS, EMEA (London) - Prisma SaaS, DLP (NGFW) APAC, DLP (NGFW) EU, Prisma Access DLP, Enterprise DLP - Americas (Brazil)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-16 11:06 UTC

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

2. investigating 2026-07-16 11:18 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-16 11:57 UTC

   We have deployed a fix and are seeing functionality begin to return to normal in some regions. We will continue to monitor the situation.

4. monitoring 2026-07-16 12:54 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 2026-07-16 13:57 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 2026-07-16 19:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 05:58 UTC

   We are currently investigating this issue.

2. identified 2026-07-10 07:19 UTC

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

3. monitoring 2026-07-10 07:24 UTC

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

4. monitoring 2026-07-10 07:27 UTC

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

5. monitoring 2026-07-10 10:05 UTC

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

6. monitoring 2026-07-10 13:09 UTC

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

7. monitoring 2026-07-10 13:10 UTC

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

8. resolved 2026-07-10 13:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Government, United States - Goverment, United States - Government

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-07 19:36 UTC

   We are currently investigating this issue.

2. identified 2026-07-07 20:07 UTC

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

3. monitoring 2026-07-07 21:30 UTC

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

4. resolved 2026-07-08 00:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: australiaeast, australiasoutheast, canadacentral, centralus, eastasia, eastus, eastus2, northeurope, uksouth, ukwest, westeurope, westus, westus2, westus3, brazilsouth, japaneast, northcentralus, southeastasia, canadaeast, centralindia, francecentral, germanywestcentral, israelcentral, italynorth, japanwest, koreacentral, mexicocentral, newzealandnorth, norwayeast, southafricanorth, southcentralus, southindia, spaincentral, swedencentral, switzerlandnorth, switzerlandwest, uaenorth, westcentralus

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. monitoring 2026-07-07 18:06 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...

2. monitoring 2026-07-08 15:45 UTC

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

3. monitoring 2026-07-10 09:16 UTC

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

4. monitoring 2026-07-12 04:49 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-07-12 04:53 UTC

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

6. monitoring 2026-07-12 04:53 UTC

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

7. monitoring 2026-07-15 15:12 UTC

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

8. monitoring 2026-07-17 12:10 UTC

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

9. monitoring 2026-07-22 05:05 UTC

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

10. monitoring 2026-07-23 20:00 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...

11. monitoring 2026-07-27 19:02 UTC

    We are continuing to monitor for any further issues.

12. monitoring 2026-08-03 07:05 UTC

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

13. monitoring 2026-09-16 15:19 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,...

14. resolved 2026-09-24 02:29 UTC

    Availability issues are now resolved

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-02 10:00 UTC

   We are currently investigating this issue.

2. identified 2026-07-02 11:22 UTC

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

3. identified 2026-07-02 13:12 UTC

   We have applied a mitigation and currently monitoring the progress.

4. identified 2026-07-02 17:09 UTC

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

5. monitoring 2026-07-02 17:16 UTC

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

6. resolved 2026-07-02 17:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Stockholm (eu-north-1)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-06-30 21:30 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...

2. resolved 2026-06-30 22:04 UTC

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

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-30 13:52 UTC

   We are currently investigating this issue.

2. resolved 2026-06-30 15:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire Singapore Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 16:15 UTC

   WildFire is currently experiencing an issue in the Singapore Cloud. We are actively working on this issue and will provide another update by 18:00 UTC with further details. Customer Impact: Intermittent failures may occur during the file upload process and while querying...

2. investigating 2026-06-29 18:01 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-29 19:42 UTC

   We are continuing to investigate this issue.

4. investigating 2026-06-29 21:46 UTC

   We are continuing to investigate this issue.

5. investigating 2026-06-29 23:38 UTC

   We are continuing to investigate this issue.

6. identified 2026-06-30 00:39 UTC

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

7. monitoring 2026-06-30 01:25 UTC

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

8. resolved 2026-06-30 01:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-29 12:57 UTC

   We are currently investigating this issue.

2. identified 2026-06-29 13:10 UTC

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

3. monitoring 2026-06-29 14:38 UTC

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

4. resolved 2026-06-29 15:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: eastasia, southeastasia, centralindia, italynorth, southafricanorth, southindia, swedencentral, uaenorth

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-25 09:33 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...

2. resolved 2026-06-25 11:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Europe - app2.eu.prismacloud.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 15:02 UTC

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

2. identified 2026-06-18 19:46 UTC

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

3. identified 2026-06-18 20:53 UTC

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

4. identified 2026-06-18 22:16 UTC

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

5. monitoring 2026-06-18 22:30 UTC

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

6. resolved 2026-06-18 23:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Netherlands - Europe, Netherlands - Europe

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-16 16:41 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...

2. resolved 2026-06-16 17:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

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), Hub, Cloud Manager Europe (Switzerland), Cloud Manager Europe (Germany), Cloud Manager APAC (Australia), Cloud Manager Middle East (Qatar), Cloud 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)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-11 00:57 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 2026-06-11 01:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: DLP (NGFW) NAM, Prisma Access DLP

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-05 17:38 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.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Americas - US - app3.prismacloud.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 22:26 UTC

   We are currently investigating this issue.

2. monitoring 2026-06-05 00:46 UTC

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

3. resolved 2026-06-05 01:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Americas

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-01 21:21 UTC

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

2. identified 2026-06-02 01:35 UTC

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

3. monitoring 2026-06-02 21:10 UTC

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

4. resolved 2026-06-02 23:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: WildFire Global Cloud

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-01 13:46 UTC

   WildFire is currently experiencing an issue in US Cloud. We are actively working on this issue and will provide another update by 14:00 with further details. Customer Impact: Error while getting verdict Workaround: N/A

2. investigating 2026-06-02 06:29 UTC

   WF is getting unexpected traffic from yesterday for which Wildfire services are not ready to handle. Wildfire has autoscaling settings. However, traffic is more than 8X of normal traffic. The max resources allocated can not handle these traffic.

3. identified 2026-06-02 07:21 UTC

   Root cause identified. The fix to be ready in a couple of hours and deployment to happen later today.

4. investigating 2026-06-02 15:28 UTC

   We are currently investigating this issue.

5. investigating 2026-06-02 15:35 UTC

   Wildfire is experiencing 8X more traffic than the normal traffic. The source of this traffic is not yet identified. We are actively working on the issue.

6. investigating 2026-06-02 19:23 UTC

   We are continuing to investigate this issue.

7. investigating 2026-06-02 21:13 UTC

   We are continuing to investigate this issue.

8. identified 2026-06-02 21:56 UTC

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

9. monitoring 2026-06-02 22:14 UTC

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

10. resolved 2026-06-02 22:55 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-06-01 03:00 UTC

   Customers might experience intermittent failures when attempting to retrieve verdicts.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: westus2

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Multiple services – Power/cooling issues in West US 2.

1. investigating 2026-05-29 08:26 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 2026-05-29 09:46 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 2026-05-29 13:33 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,...

4. resolved 2026-05-30 03:49 UTC

   Azure team confirmed that this incident had been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Americas - US - app.prismacloud.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-21 21:04 UTC

   We are currently investigating this issue.

2. identified 2026-05-21 21:04 UTC

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

3. monitoring 2026-05-21 22:01 UTC

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

4. resolved 2026-05-21 22:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-05-22 21:30 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,...

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-18 08:50 UTC

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

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: United States - Government, United States - Goverment, United States - Government

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-14 18:11 UTC

   We are currently investigating this issue.

2. identified 2026-05-14 18:17 UTC

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

3. monitoring 2026-05-14 20:18 UTC

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

4. resolved 2026-05-14 22:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.

Affected: Americas - US - app4.prismacloud.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-14 05:33 UTC

   We are currently investigating this issue.

2. investigating 2026-05-14 05:53 UTC

   We are continuing to investigate this issue.

3. identified 2026-05-14 06:00 UTC

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

4. monitoring 2026-05-14 06:07 UTC

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

5. resolved 2026-05-14 06:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Palo Alto Networks's status page.