Palo Alto Networks Outage History

Palo Alto Networks degraded View live status →

There were 67 Palo Alto Networks outages since February 3, 2026 totaling 219h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.paloaltonetworks.com

Notice April 29, 2026

WildFire Japan Cloud Service Scheduled Maintenance

Detected by Pingoru
Apr 29, 2026, 12:17 AM UTC
Resolved
Apr 29, 2026, 08:32 PM UTC
Duration
20h 15m
Affected: WildFire Japan Cloud
Timeline · 3 updates
  1. scheduled Apr 29, 2026, 12:17 AM UTC

    We have a planned service maintenance for WildFire Japan Cloud on April 29, 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. scheduled Apr 29, 2026, 06:00 PM UTC

    Maintenance will begin as scheduled in 60 minutes.

  3. in progress Apr 29, 2026, 07:00 PM UTC

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

Read the full incident report →

Notice April 28, 2026

WildFire Italy Cloud Service Scheduled Maintenance

Detected by Pingoru
Apr 28, 2026, 08:54 PM UTC
Resolved
Apr 28, 2026, 10:02 PM UTC
Duration
1h 8m
Affected: WildFire Italy Cloud
Timeline · 2 updates
  1. scheduled Apr 28, 2026, 08:54 PM UTC

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

  2. in progress Apr 28, 2026, 09:00 PM UTC

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

Read the full incident report →

Notice April 28, 2026

WildFire Brazil Cloud Service Scheduled Maintenance

Detected by Pingoru
Apr 28, 2026, 08:54 PM UTC
Resolved
Apr 28, 2026, 10:02 PM UTC
Duration
1h 8m
Timeline · 2 updates
  1. scheduled Apr 28, 2026, 08:54 PM UTC

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

  2. in progress Apr 28, 2026, 09:01 PM UTC

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

Read the full incident report →

Notice April 28, 2026

WildFire Delhi Cloud Service Scheduled Maintenance

Detected by Pingoru
Apr 28, 2026, 05:11 PM UTC
Resolved
Apr 28, 2026, 06:36 PM UTC
Duration
1h 25m
Timeline · 2 updates
  1. scheduled Apr 28, 2026, 05:11 PM UTC

    We have a planned service maintenance for WildFire Delhi Cloud on April 28, 2026 from 17:30:00 UTC to 18:30:00 UTC. Customer Impact: Customers may encounter intermittent disconnection during the maintenance window and detection delays.

  2. in progress Apr 28, 2026, 05:30 PM UTC

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

Read the full incident report →

Minor April 27, 2026

Azure France Central outage impacting Cloud NGFW Services.

Detected by Pingoru
Apr 27, 2026, 12:02 PM UTC
Resolved
Apr 27, 2026, 08:13 PM UTC
Duration
8h 11m
Affected: francecentral
Timeline · 5 updates
  1. investigating Apr 27, 2026, 12:02 PM UTC

    We have identified an issue with Azure affecting the Cloud NGFW France Central region. Azure Brazil South region experiencing Storage & Cosmos DB issue which is impacting CNGFW Services. Customers may experience intermittent service unavailability, degraded performance, or delays in monitoring and telemetry. Current Status : Azure notified higher than expected latency, timeouts or HTTP 500 errors when accessing data stored on Storage & CosmoDB accounts hosted in this region. We are actively investigating and mitigation actions are currently in progress to stabilize connectivity. Ongoing Actions: Our engineering team is working closely with the Azure team to restore full service. You can also monitor the underlying platform status via the Azure Service Page. 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://app.azure.com/h/GHHC-K4Z/97cdb5. Next Update: 1 PM UTC 27th Apr 2026

  2. identified Apr 27, 2026, 12:31 PM UTC

    Azure is currently experiencing a degradation in the availability of the Azure Cosmos DB service in the France Central region. https://app.azure.com/h/GHHC-K4Z/97cdb5

  3. identified Apr 27, 2026, 02:38 PM UTC

    Azure Reported Service Disruption Affecting Multiple Azure Services in the France Central Region Including Service Bus, Storage, Azure Cosmos DB experiencing an interruption when customers encountered VM restarts, temporary unavailability, and intermittent access issues due to an underlying datacenter event.

  4. monitoring Apr 27, 2026, 03:48 PM UTC

    Azure has repoted that the affected services have largely recovered; however, some dependent services are still completing recovery and may experience intermittent issues while teams continue monitoring service stability. Our teams are monitoring the affected resources to validate the restoration of functionality. The next update will be provided within 60 minutes, or sooner if there are significant developments. https://app.azure.com/h/GHHC-K4Z/97cdb5

  5. resolved Apr 27, 2026, 08:13 PM UTC

    Azure has reported that this issue is now mitigated. See https://app.azure.com/h/GHHC-K4Z/97cdb5 for an update with more information provided by Azure. CNGFW services are no longer impacted.

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 →

Critical April 17, 2026

Prisma Cloud Incident [APP.JP] - Major outage

Detected by Pingoru
Apr 17, 2026, 08:38 PM UTC
Resolved
Apr 17, 2026, 10:29 PM UTC
Duration
1h 51m
Affected: Asia Pacific - Japan - app.jp.prismacloud.io
Timeline · 5 updates
  1. investigating Apr 17, 2026, 08:38 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 17, 2026, 08:39 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 17, 2026, 09:34 PM UTC

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

  4. monitoring Apr 17, 2026, 09:58 PM UTC

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

  5. resolved Apr 17, 2026, 10:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 17, 2026

DNS Security issue

Detected by Pingoru
Apr 17, 2026, 04:00 PM UTC
Resolved
Apr 17, 2026, 04:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 17, 2026, 09:47 PM UTC

    There was a DNS security service issue that occurred at 9:03 AM PDT in the us-central1 region and has been resolved at 10:15 AM PDT. Customer Impact: This issue may cause the customers in us-central1 to experience high latency with the DNS security service.

Read the full incident report →

Minor April 16, 2026

Enterprise DLP - No Incidents in UIM in US region

Detected by Pingoru
Apr 16, 2026, 10:14 PM UTC
Resolved
Apr 17, 2026, 02:24 AM UTC
Duration
4h 10m
Affected: DLP (NGFW) NAMPrisma Access DLP
Timeline · 4 updates
  1. identified Apr 16, 2026, 10:14 PM UTC

    We've identified the issue and currently attempting to remediate. We will update in next 60 mins on progress.

  2. monitoring Apr 16, 2026, 11:11 PM UTC

    We've deployed a fix, and are seeing improvements. We'll keep monitoring for the next 2 hours. We will provide an update in the next hour on the progress.

  3. monitoring Apr 16, 2026, 11:59 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Apr 17, 2026, 02:24 AM UTC

    The issue has been resolved and all incident should now be viewable in UIM.

Read the full incident report →

Notice April 9, 2026

Prisma Cloud Incident [APP3] - Delayed asset ingestion

Detected by Pingoru
Apr 09, 2026, 06:14 PM UTC
Resolved
Apr 10, 2026, 09:32 PM UTC
Duration
1d 3h
Timeline · 8 updates
  1. investigating Apr 09, 2026, 06:14 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 09, 2026, 06:22 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 09, 2026, 07:55 PM UTC

    We are continuing to investigate this issue.

  4. identified Apr 09, 2026, 08:54 PM UTC

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

  5. identified Apr 10, 2026, 01:44 AM UTC

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

  6. identified Apr 10, 2026, 09:18 AM UTC

    Monitoring: We have applied a mitigation and monitoring the system closely.

  7. monitoring Apr 10, 2026, 12:16 PM UTC

    A mitigation is applied and we are closely monitoring our system.

  8. resolved Apr 10, 2026, 09:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 8, 2026

Prisma Cloud Incident [APP.CA] - Alerts unavailable

Detected by Pingoru
Apr 08, 2026, 04:36 PM UTC
Resolved
Apr 08, 2026, 05:50 PM UTC
Duration
1h 14m
Timeline · 5 updates
  1. investigating Apr 08, 2026, 04:36 PM UTC

    We are currently investigating this issue.

  2. investigating Apr 08, 2026, 04:41 PM UTC

    We are continuing to investigate this issue.

  3. identified Apr 08, 2026, 05:48 PM UTC

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

  4. monitoring Apr 08, 2026, 05:50 PM UTC

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

  5. resolved Apr 08, 2026, 05:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 1, 2026

WildFire Issue

Detected by Pingoru
Apr 01, 2026, 09:34 AM UTC
Resolved
Apr 01, 2026, 02:31 PM UTC
Duration
4h 57m
Affected: WildFire Global CloudWildFire Europe CloudWildFire Singapore CloudWildFire Japan CloudWildFire UK CloudWildFire U.S. Government CloudWildFire Canada CloudWildFire Australia CloudWildFire Germany CloudWildFire India CloudWildFire Switzerland CloudWildFire Poland CloudWildFire Indonesia CloudWildFire Taiwan CloudWildFire France CloudWildFire Qatar CloudWildFire South Korea CloudWildFire Israel CloudWildFire Saudi Arabia CloudWildFire Italy CloudWildfire Spain CloudWildFire South Africa CloudWildFire EU Regulated CloudWildFire US Native CloudWildFire Delhi CloudWildFire Brazil Cloud
Timeline · 3 updates
  1. investigating Apr 01, 2026, 09:34 AM UTC

    WildFire is currently experiencing an issue in all the the Clouds. We are actively working on this issue and will provide another update by 11:30 AM with further details. Customer Impact: Unable to access the Wildfire cloud regional portals Workaround: N/A

  2. monitoring Apr 01, 2026, 02:11 PM UTC

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

  3. resolved Apr 01, 2026, 02:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 26, 2026

app-ca: Maintenance extension

Detected by Pingoru
Mar 26, 2026, 08:35 AM UTC
Resolved
Mar 26, 2026, 09:41 AM UTC
Duration
1h 5m
Timeline · 2 updates
  1. investigating Mar 26, 2026, 08:35 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 26, 2026, 09:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 25, 2026

Prisma Cloud [APP2]: Ongoing service disruption

Detected by Pingoru
Mar 25, 2026, 12:05 AM UTC
Resolved
Mar 25, 2026, 02:37 AM UTC
Duration
2h 32m
Affected: Americas - US - app2.prismacloud.io
Timeline · 3 updates
  1. investigating Mar 25, 2026, 12:05 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 25, 2026, 01:55 AM UTC

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

  3. resolved Mar 25, 2026, 02:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 20, 2026

Investigating Cortex Federal Certificate Issue

Detected by Pingoru
Mar 20, 2026, 07:43 PM UTC
Resolved
Mar 21, 2026, 03:30 AM UTC
Duration
7h 46m
Affected: United States - GovernmentUnited States - GovermentUnited States - GovernmentUnited States - GovernmentFedRAMP Moderate
Timeline · 4 updates
  1. investigating Mar 20, 2026, 07:43 PM UTC

    We are currently investigating an issue with certificates in our Cortex Federal Environment. Agent local protection is not affected.

  2. identified Mar 20, 2026, 07:55 PM UTC

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

  3. monitoring Mar 20, 2026, 08:11 PM UTC

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

  4. resolved Mar 21, 2026, 03:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Prisma Cloud Incident - Delayed Ingestion [APP3]

Detected by Pingoru
Mar 18, 2026, 09:05 PM UTC
Resolved
Mar 19, 2026, 04:28 PM UTC
Duration
19h 23m
Affected: Americas - US - app3.prismacloud.io
Timeline · 3 updates
  1. investigating Mar 18, 2026, 09:05 PM UTC

    We are currently investigating this issue.

  2. identified Mar 18, 2026, 09:05 PM UTC

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

  3. resolved Mar 19, 2026, 04:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 16, 2026

Prisma Cloud Issue - Stale Data [APP3]

Detected by Pingoru
Mar 16, 2026, 10:56 PM UTC
Resolved
Mar 17, 2026, 09:15 PM UTC
Duration
22h 19m
Timeline · 4 updates
  1. investigating Mar 16, 2026, 10:56 PM UTC

    We are currently investigating this issue.

  2. identified Mar 16, 2026, 10:57 PM UTC

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

  3. identified Mar 17, 2026, 07:48 PM UTC

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

  4. resolved Mar 18, 2026, 02:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 12, 2026

Prisma Cloud not available in China regions due to extended maintenance

Detected by Pingoru
Mar 12, 2026, 11:08 PM UTC
Resolved
Mar 13, 2026, 06:57 PM UTC
Duration
19h 48m
Affected: China - app.prismacloud.cn
Timeline · 6 updates
  1. investigating Mar 12, 2026, 11:08 PM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2026, 11:12 PM UTC

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

  3. identified Mar 13, 2026, 03:18 AM UTC

    Prisma Cloud continues to be unavailable in China regions. Services are presently and gradually resuming operations, but the application will be in a degraded state until the next update.

  4. identified Mar 13, 2026, 07:15 AM UTC

    Prisma Cloud continues to be unavailable in China regions. While parts of the site may become accessible at times, backend services may still be in a degraded state.

  5. monitoring Mar 13, 2026, 06:16 PM UTC

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

  6. resolved Mar 13, 2026, 06:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 12, 2026

APP: Asset inventory page degradation

Detected by Pingoru
Mar 12, 2026, 04:01 AM UTC
Resolved
Mar 12, 2026, 05:25 AM UTC
Duration
1h 23m
Timeline · 2 updates
  1. investigating Mar 12, 2026, 04:01 AM UTC

    We are currently investigating this issue.

  2. resolved Mar 12, 2026, 05:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

Cloud NGFW managed by Strata Cloud Manager(SCM) impacted - Commit issues

Detected by Pingoru
Mar 11, 2026, 06:57 PM UTC
Resolved
Mar 13, 2026, 04:37 AM UTC
Duration
1d 9h
Affected: N.Virginia (us-east-1)Ohio (us-east-2)australiaeastN.California (us-west-1)australiasoutheastOregon (us-west-2)canadacentralCape Town (af-south-1)centralusHong Kong (ap-east-1)eastasiaeastusHyderabad (ap-south-2)eastus2Melbourne (ap-southeast-4)northeuropeMumbai (ap-south-1)Osaka (ap-northeast-3)uksouthukwestSeoul (ap-northeast-2)Singapore (ap-southeast-1)westeuropeSydney (ap-southeast-2)westusTokyo (ap-northeast-1)westus2Canada Central (ca-central-1)westus3brazilsouthCalgary (ca-west-1)Frankfurt (eu-central-1)japaneastIreland (eu-west-1)northcentralusLondon (eu-west-2)southeastasiaMilan (eu-south-1)canadaeastParis (eu-west-3)centralindiafrancecentralSpain (eu-south-2)Stockholm (eu-north-1)germanywestcentralBahrain (me-south-1)israelcentralSao Paulo(sa-east-1)italynorthjapanwestkoreacentralmexicocentralnewzealandnorthnorwayeastsouthafricanorthsouthcentralussouthindiaspaincentralswedencentralswitzerlandnorthswitzerlandwestuaenorthwestcentralus
Timeline · 4 updates
  1. identified Mar 11, 2026, 06:57 PM UTC

    We are investigating reports of Commit Failures for CNGFW firewalls managed by Strata Cloud Manager (SCM). This prevents customers from pushing config into the Firewalls. Note: Data plane traffic and security enforcement are not impacted by this event. Ongoing Actions: Engineers have identified the issue and are now working on resolving the issue. Next Update: [11:00 PM UTC], [March 11, 2026]

  2. identified Mar 12, 2026, 03:05 AM UTC

    We are investigating reports of Commit Failures for AWS CNGFW firewalls managed by Strata Cloud Manager (SCM). This prevents customers from pushing config into the Firewalls. Note: Data plane traffic and security enforcement are not impacted by this event. Ongoing Actions: Engineers have identified the issue and are now working on resolving the issue. Next Update: [09:00 AM UTC], [March 12, 2026]

  3. monitoring Mar 12, 2026, 04:20 AM UTC

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

  4. resolved Mar 18, 2026, 04:37 AM UTC

    This issue has been resolved

Read the full incident report →

Minor March 11, 2026

Azure West US 3, West Europe & Central US Network issues  impacting Cloud NGFW Services

Detected by Pingoru
Mar 11, 2026, 05:11 AM UTC
Resolved
Mar 11, 2026, 09:38 AM UTC
Duration
4h 26m
Affected: centraluswesteuropewestus3
Timeline · 4 updates
  1. investigating Mar 11, 2026, 05:11 AM UTC

    Azure West US 3, West Europe & Central US regions experiencing Intermittent Network connectivity issue which may be impacting CNGFW Services. Ongoing Actions: Our engineering team is working closely with the Azure team. Azure status updates can be tracked through the Service Page. West US 3 https://app.azure.com/h/TGDZ-X10/0858a9 Central US https://app.azure.com/h/PG9P-X40/4cd327 West Europe https://app.azure.com/h/8ZSP-XL0/35bdc8

  2. investigating Mar 11, 2026, 05:49 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Mar 11, 2026, 08:17 AM UTC

    Azure has mitigated the underlying intermittent network issue. We are monitoring for continued stability.

  4. resolved Mar 11, 2026, 09:38 AM UTC

    Azure notified services has been restored.

Read the full incident report →

Major March 10, 2026

Customer Service Portal is having intermittent connectivity issues

Detected by Pingoru
Mar 10, 2026, 05:30 PM UTC
Resolved
Mar 10, 2026, 06:22 PM UTC
Duration
52m
Affected: Customer Support Portal
Timeline · 3 updates
  1. investigating Mar 10, 2026, 05:30 PM UTC

    Intermittent connectivity issues were first observed at 9:41 AM PDT. We are actively investigating the issue.

  2. monitoring Mar 10, 2026, 05:52 PM UTC

    The problem has been mitigated , we will continue monitoring this incident

  3. resolved Mar 10, 2026, 06:22 PM UTC

    Incident is resolved

Read the full incident report →

Looking to track Palo Alto Networks downtime and outages?

Pingoru polls Palo Alto Networks's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Palo Alto Networks reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Palo Alto Networks alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Palo Alto Networks for free

5 free monitors · No credit card required