Palo Alto Networks Outage History

Palo Alto Networks is up right now

Pingoru has recorded 569 incidents for Palo Alto Networks: 569 in the last 12 months and 352 in the last 90 days.

Source: status.paloaltonetworks.com

569incidents recorded
569last 12 months
352last 90 days
17 hourstypical duration
Incidents per month
0100200AprMayJunJulAugSepOct123
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct28%
Pingoru began tracking Palo Alto Networks in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20263887 of 720 (12%)
May 202643163 of 744 (22%)
June 202668134 of 720 (19%)
July 202648406 of 744 (55%)
August 202687463 of 744 (62%)
September 2026119118 of 720 (16%)
October 2026123167 of 594 (28%)

Incidents, newest first

Minor March 10, 2026 Azure impacting Cloud NGFW New Firewall Creation. 10h 6m australiaeast, australiasoutheast, canadacentral, centralus and 34 more

Started Mar 10, 2026, 12:41 PM UTC· resolved Mar 10, 2026, 10:47 PM UTC

  1. investigating Mar 10, 2026, 12:41 PM UTC

    We have identified an issue with Azure affecting the Cloud NGFW Customers may experience delays/failures to deploy new resources Ongoing Actions: Our engineering team is working closely with the azure and We are working with the azure team to restore the services

  2. investigating Mar 10, 2026, 02:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 10, 2026, 02:58 PM UTC

    We are continuing to investigate this issue.

  4. resolved Mar 10, 2026, 10:47 PM UTC

    The resolution has been implemented across all regions. We confirm the successful deployment of the fix and will continue to monitor the sanity jobs.

Read the full incident report →

Critical March 6, 2026 ADNS/ADNSR - False Positive Detection Incident 1m ADNS Resolver 96.9.97.9, ADNS Resolver 96.9.96.9

Started Mar 06, 2026, 08:22 PM UTC· resolved Mar 06, 2026, 08:24 PM UTC

  1. investigating Mar 06, 2026, 08:22 PM UTC

    One of our detectors is experiencing an issue that caused false positive blocking. Specifically, res-stls-prod[.]edgesuite[.]net.globalredir[.]akadns88[.]net was misclassified as phishing from 3/6/2026 13:08 UTC to 3/6/2026 16:50 UTC. This domain is a CNAME of res.cdn.office[.]net and res-stls-prod.edgesuite[.]net. So, the DNS resolution of res.cdn.office[.]net or res-stls-prod.edgesuite[.]net might experience blockage during the period of time mentioned above.

  2. investigating Mar 06, 2026, 08:23 PM UTC

    We have disabled the false positive signature to resume customer utility. We are continuing to investigate the root cause.

  3. resolved Mar 06, 2026, 08:24 PM UTC

    This incident has been resolved. We have identified the root cause. The incorrect verdict was due to multiple 3rd party intelligence feeds providing malicious verdicts. Enhancement measure will be added to reduce false positives caused by CNAME domains from 3rd party intelligence ingestions.

Read the full incident report →

Major March 3, 2026 edgeService (IoT) service downgrade in United States 1h 57m United States - Americas

Started Mar 03, 2026, 11:10 PM UTC· resolved Mar 04, 2026, 01:07 AM UTC

  1. investigating Mar 03, 2026, 11:10 PM UTC

    The edgeService stop to fetch latest verdicts from backend service. We have identified the issue in upstream component. We are monitoring the upstream service and will post the update here.

  2. resolved Mar 04, 2026, 01:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026 IoT Security (United States) Outage 6h 21m United States

Started Mar 03, 2026, 06:25 PM UTC· resolved Mar 04, 2026, 12:46 AM UTC

  1. investigating Mar 03, 2026, 06:25 PM UTC

    The IoT service in the US is currently experiencing a portal access issue due to a database outage. As a result, US customers may have difficulties accessing the IoT portal at this time. The team is actively working to resolve the issue and will provide an update shortly.

  2. investigating Mar 03, 2026, 09:49 PM UTC

    The team is actively investigating the ongoing issue impacting the IoT service in the US. Efforts are focused on recovering the affected systems and restoring portal access for our customers. We will provide further updates as soon as more information is available. Thanks,

  3. investigating Mar 03, 2026, 11:56 PM UTC

    The IoT US Portal is currently recovering as connection limits have been stabilized and services are returning to baseline levels.

  4. monitoring Mar 04, 2026, 12:08 AM UTC

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

  5. resolved Mar 04, 2026, 12:46 AM UTC

    Status: Service is fully Restored Summary: The technical team has successfully addressed the underlying database issue and restored all affected services to full functionality. Details: Data integrity has been verified, and all system components are now operating within normal parameters. We are continuing to monitor the environment closely to ensure ongoing stability.

Read the full incident report →

Minor March 3, 2026 Prisma Cloud delayed asset ingestion [app2, app3, app4, app-eu, app-ind, app, app2-eu] 10h 13m

Started Mar 03, 2026, 05:30 PM UTC· resolved Mar 04, 2026, 03:44 AM UTC

  1. investigating Mar 03, 2026, 05:30 PM UTC

    We are currently investigating this issue.

  2. investigating Mar 03, 2026, 05:32 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 03, 2026, 05:33 PM UTC

    We are continuing to investigate this issue.

  4. identified Mar 04, 2026, 12:42 AM UTC

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

  5. resolved Mar 04, 2026, 03:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 3, 2026 Prisma Cloud partial degraded performance [APP2] 15h 54m

Started Mar 03, 2026, 01:04 AM UTC· resolved Mar 03, 2026, 04:59 PM UTC

  1. investigating Mar 03, 2026, 01:04 AM UTC

    We are currently investigating this issue.

  2. identified Mar 03, 2026, 01:19 AM UTC

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

  3. monitoring Mar 03, 2026, 03:46 AM UTC

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

  4. resolved Mar 03, 2026, 04:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026 AWS Middle East(Bahrain) outage impacting Cloud NGFW Services. 232d 19h Bahrain (me-south-1)

Started Mar 02, 2026, 10:49 PM UTC· resolved Oct 21, 2026, 06:29 PM UTC

  1. monitoring Mar 02, 2026, 10:49 PM UTC

    AWS Middle East(Bahrain) outage impacting Cloud NGFW Services. We are aware of power outage in AWS Bahrain region. We are evaluating the impact on Cloud NGFW services in this region. Customers may experience failures to deploy new resources in this region. 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 Status Page: https://health.aws.amazon.com/health/status?path=service-history Next Update: 5:00PM 3/03/2026 UTC.

  2. monitoring Mar 03, 2026, 03:10 AM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Mar 03, 2026, 07:06 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Apr 02, 2026, 06:05 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 21, 2026, 06:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 28, 2026 Azure Brazil South outage impacting CNGFW services 1h 59m brazilsouth

Started Feb 28, 2026, 07:59 AM UTC· resolved Feb 28, 2026, 09:59 AM UTC

  1. investigating Feb 28, 2026, 07:59 AM UTC

    Azure Brazil South region experiencing Intermittent Network connectivity issue which is impacting CNGFW Services. Customers may experience intermittent service unavailability, degraded performance, or delays in monitoring and telemetry. Current Status : Azure notified intermittent connectivity and packet loss issue affecting network traffic to and from 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. https://app.azure.com/h/CQLF-C40/3f4a19

  2. monitoring Feb 28, 2026, 09:37 AM UTC

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

  3. monitoring Feb 28, 2026, 09:42 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 28, 2026, 09:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 26, 2026 Incorrect Verdicts Issued in WildFire 3h 55m

Started Feb 26, 2026, 07:34 PM UTC· resolved Feb 26, 2026, 11:30 PM UTC

  1. identified Feb 26, 2026, 07:34 PM UTC

    WildFire analysis on February 25, 2026, PST, resulted in an incorrect verdict for a specific set of files. We are currently correcting the verdicts for all affected files.

  2. resolved Feb 26, 2026, 11:30 PM UTC

    By 1:00 PM PST on February 26, 2026, the verdicts for all affected files have been corrected.

Read the full incident report →

Minor February 20, 2026 Customers are unable to add comments to existing support cases 14m Customer Support Portal

Started Feb 20, 2026, 04:06 AM UTC· resolved Feb 20, 2026, 04:21 AM UTC

  1. identified Feb 20, 2026, 04:06 AM UTC

    Adding new comments to support cases is currently unavailable. The issue has been identified and a fix is being implemented.

  2. resolved Feb 20, 2026, 04:21 AM UTC

    The issue has been resolved and adding comments is now functional.

Read the full incident report →

Notice February 12, 2026 AURL/ADNS - False Positive Detection Incident –

Started Feb 12, 2026, 05:00 PM UTC· resolved Feb 12, 2026, 05:00 PM UTC

  1. resolved Feb 14, 2026, 12:14 AM UTC

    Briefly during the morning of 2/12/2026, the domain svc.ha-teams.office.com was miscategorized within AURL filtering and ADNS products. This may have caused interruptions in Microsoft Teams traffic. The issue has been resolved.

Read the full incident report →

Minor February 11, 2026 Azure Resource Manager East US 2, South Central US & West US 3 Impacting CNGFW services 6h 25m centralus, eastus2, westus3

Started Feb 11, 2026, 04:03 AM UTC· resolved Feb 11, 2026, 10:29 AM UTC

  1. investigating Feb 11, 2026, 04:03 AM UTC

    Azure East US 2, South Central US & West US 3 Resource Manager impacting CNGFW services. Customers may experience intermittent service unavailability, degraded performance, or delays in on creating firewall where Public IP is needed. It would not impact already created Firewall resources. Ongoing Actions: Our engineering team is working closely with the Azure team. Further updates on the underlying azure platform status can be followed through the Azure Status Page. https://app.azure.com/h/B_6T-NXZ/418272

  2. monitoring Feb 11, 2026, 06:44 AM UTC

    CNGFW Services continues to remain being monitored & currently No impact detected.

  3. resolved Feb 11, 2026, 10:29 AM UTC

    CNGFW Services continues to operate normally & no impact observed.

Read the full incident report →

Major February 9, 2026 App-ca partial outage - Inventory and compliance pages are impacted 11h 38m

Started Feb 09, 2026, 12:11 PM UTC· resolved Feb 09, 2026, 11:50 PM UTC

  1. investigating Feb 09, 2026, 12:11 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 09, 2026, 01:13 PM UTC

    We have engaged all relevant teams and are actively investigating the issue with the highest priority. Further updates will be shared as soon as more information is available.

  3. resolved Feb 09, 2026, 11:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 7, 2026 Azure US West outage impacting CNGFW services 7h 50m westus, westus2, westus3

Started Feb 07, 2026, 05:04 PM UTC· resolved Feb 08, 2026, 12:55 AM UTC

  1. investigating Feb 07, 2026, 05:04 PM UTC

    Azure US West outage impacting CNGFW Services. We have identified an Azure outage affecting the Cloud NGFW West US region. Customers may experience intermittent service unavailability, degraded performance, or delays in monitoring and telemetry. Current Status: Earlier today, an unexpected utility power interruption at a Azure West US datacenter caused a partial facility outage. While backup power systems engaged immediately and utility power has since been stabilized, some infrastructure components were temporarily affected. 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 Status Page. https://azure.status.microsoft/en-us/status Next Update: 01:30 UTC, 08 February 2026

  2. investigating Feb 07, 2026, 05:21 PM UTC

    The Azure outage that impacted your CNGFW service is now resolved and your service is back up. The firewall resources that were experiencing service degradation has been restored. Please contact Palo Alto Networks support team to address any concerns. Thank you,

  3. resolved Feb 08, 2026, 12:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 6, 2026 We are experiencing an issue with login to Cortex Cloud products console 1h 16m Australia, Australia, Australia, Australia and 84 more

Started Feb 06, 2026, 02:42 PM UTC· resolved Feb 06, 2026, 03:59 PM UTC

  1. investigating Feb 06, 2026, 02:42 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 06, 2026, 03:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 4, 2026 AI Runtime Security (AIRS) Cloud - Partial Outage in the United States region 1h 30m United States - Americas

Started Feb 04, 2026, 09:15 PM UTC· resolved Feb 04, 2026, 10:45 PM UTC

  1. investigating Feb 10, 2026, 07:44 AM UTC

    We are currently investigating this issue. Customer Impact: Customer Firewalls may be unable to send data to the AIRS Cloud in the United States region.

  2. resolved Feb 10, 2026, 07:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 2, 2026 Datat Security: UI Service Disruption 9h 6m SaaS API - North America, SaaS API - Singapore, SaaS API - Frankfurt, SaaS API - India and 4 more

Started Feb 02, 2026, 09:08 AM UTC· resolved Feb 02, 2026, 06:15 PM UTC

  1. investigating Feb 02, 2026, 09:08 AM UTC

    Engineering teams are investigating an issue that may be impacting functionality for a subset of features within the Data Security UI across multiple pages.

  2. resolved Feb 02, 2026, 06:54 PM UTC

    Engineering teams have resolved the issue impacting customers.

Read the full incident report →

Minor January 28, 2026 Prisma Cloud Incident - [app2] - Snapshot service experiencing partial outage 16m

Started Jan 28, 2026, 03:44 PM UTC· resolved Jan 28, 2026, 04:00 PM UTC

  1. investigating Jan 28, 2026, 03:44 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 28, 2026, 04:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 26, 2026 Prisma Cloud Ingestion Delay [APP4] 20h 36m Americas - US - app4.prismacloud.io

Started Jan 26, 2026, 03:15 PM UTC· resolved Jan 27, 2026, 11:52 AM UTC

  1. investigating Jan 26, 2026, 03:15 PM UTC

    Prisma Cloud is currently experiencing an issue. We are actively working on this issue and will provide another update once available with further details. Customer Impact: Delayed ingestion of cloud resources Workaround: N/A

  2. investigating Jan 26, 2026, 11:05 PM UTC

    We have identified increased latency delaying ingestion for Azure cloud. We are continuing to investigate and work on a fix.

  3. resolved Jan 27, 2026, 11:52 AM UTC

    This incident has been resolved

Read the full incident report →

Major January 21, 2026 Prisma Cloud Compute incident [APP.ID] 2h 18m

Started Jan 21, 2026, 07:13 PM UTC· resolved Jan 21, 2026, 09:32 PM UTC

  1. investigating Jan 21, 2026, 07:13 PM UTC

    We are currently investigating this issue.

  2. identified Jan 21, 2026, 07:51 PM UTC

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

  3. monitoring Jan 21, 2026, 07:56 PM UTC

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

  4. resolved Jan 21, 2026, 09:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 15, 2026 Service Degradation affecting Cloud NGFW Azure 3h 30m australiaeast, australiasoutheast, canadacentral, centralus and 14 more

Started Jan 15, 2026, 06:41 PM UTC· resolved Jan 15, 2026, 10:12 PM UTC

  1. investigating Jan 15, 2026, 06:41 PM UTC

    Status: Service Degradation Summary: We are currently experiencing an issue with the service provider affecting Cloud NGFW Azure onboarding and Azure Portal integration. Impact: Onboarding: New onboarding activities for Cloud NGFW Azure Service via Strata Cloud Manager (SCM) are currently unavailable. Support Access: The support page within the Azure portal is intermittently unavailable. Workaround: Customers requiring technical assistance should bypass the Azure portal and log cases directly via the Palo Alto Networks Support Portal. Next Steps: Our engineering teams are actively working toward a resolution. We will provide updates every 4 hours. Next Update: 22:45UTC Jan15th, 2025

  2. resolved Jan 15, 2026, 10:12 PM UTC

    Issue has been completely resolved

Read the full incident report →

Major January 15, 2026 Strata Logging Service - Issue in FedRAMP Moderate 21h 59m United States - Government Moderate

Started Jan 15, 2026, 05:35 PM UTC· resolved Jan 16, 2026, 03:35 PM UTC

  1. investigating Jan 15, 2026, 05:35 PM UTC

    Strata Logging Service is currently experiencing an issue in FedRAMP Moderate. We are actively working on this issue and will provide another update by 19:00 UTC with further details. Customer Impact: Log queries are slow or timing out starting at around 15:55 UTC. Log ingestion is unaffected. Workaround: N/A

  2. monitoring Jan 15, 2026, 06:42 PM UTC

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

  3. resolved Jan 16, 2026, 03:35 PM UTC

    CDL service is fully operational

Read the full incident report →