Palo Alto Networks Outage History

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

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

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

Source: https://status.paloaltonetworks.com

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 →

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 →

Minor March 10, 2026

Azure impacting Cloud NGFW New Firewall Creation.

Detected by Pingoru
Mar 10, 2026, 12:41 PM UTC
Resolved
Mar 10, 2026, 10:47 PM UTC
Duration
10h 6m
Affected: australiaeastaustraliasoutheastcanadacentralcentraluseastasiaeastuseastus2northeuropeuksouthukwestwesteuropewestuswestus2westus3brazilsouthjapaneastnorthcentralussoutheastasiacanadaeastcentralindiafrancecentralgermanywestcentralisraelcentralitalynorthjapanwestkoreacentralmexicocentralnewzealandnorthnorwayeastsouthafricanorthsouthcentralussouthindiaspaincentralswedencentralswitzerlandnorthswitzerlandwestuaenorthwestcentralus
Timeline · 4 updates
  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

Detected by Pingoru
Mar 06, 2026, 08:22 PM UTC
Resolved
Mar 06, 2026, 08:24 PM UTC
Duration
1m
Affected: ADNS Resolver 96.9.97.9ADNS Resolver 96.9.96.9
Timeline · 3 updates
  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

Detected by Pingoru
Mar 03, 2026, 11:10 PM UTC
Resolved
Mar 04, 2026, 01:07 AM UTC
Duration
1h 57m
Affected: United States - Americas
Timeline · 2 updates
  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

Detected by Pingoru
Mar 03, 2026, 06:25 PM UTC
Resolved
Mar 04, 2026, 12:46 AM UTC
Duration
6h 21m
Affected: United States
Timeline · 5 updates
  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]

Detected by Pingoru
Mar 03, 2026, 05:30 PM UTC
Resolved
Mar 04, 2026, 03:44 AM UTC
Duration
10h 13m
Timeline · 5 updates
  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]

Detected by Pingoru
Mar 03, 2026, 01:04 AM UTC
Resolved
Mar 03, 2026, 04:59 PM UTC
Duration
15h 54m
Timeline · 4 updates
  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.

Detected by Pingoru
Mar 02, 2026, 04:51 PM UTC
Resolved
Mar 02, 2026, 09:49 PM UTC
Duration
4h 58m
Affected: Bahrain (me-south-1)
Timeline · 2 updates
  1. identified Mar 02, 2026, 04:51 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: 9:00PM 3/02/2026 UTC.

  2. resolved Mar 02, 2026, 09:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 28, 2026

Azure Brazil South outage impacting CNGFW services

Detected by Pingoru
Feb 28, 2026, 07:59 AM UTC
Resolved
Feb 28, 2026, 09:59 AM UTC
Duration
1h 59m
Affected: brazilsouth
Timeline · 4 updates
  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 →