Is Palo Alto Networks down?

Last checked 2m ago
Current status
Palo Alto Networks is reporting minor issues

About Palo Alto Networks. Palo Alto Networks makes network firewalls and the Prisma and Cortex cloud security products.

Palo Alto Networks is reporting minor issues right now (last checked 2m ago).

Real-time Palo Alto Networks status, recent outages, and incident history: pulled directly from Palo Alto Networks's official status page at status.paloaltonetworks.com every 5 minutes. Pingoru tracks 531 Palo Alto Networks services and has captured 22 incidents in the last 90 days (99.71% uptime). Get email, Slack, Discord, or webhook alerts the moment Palo Alto Networks reports a new incident, free for 3 monitors, no credit card.

Users who monitor Palo Alto Networks also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 KnowBe4 Incapsula SentinelOne Keeper Canary View all 8,000+ providers
Palo Alto Networks uptime 99.71% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 10m
    Started Nov 10, 2026, 10:05 AM UTC · Resolved Nov 10, 2026, 12:16 PM UTC
    Americas - US - app.prismacloud.io
    Timeline · 2 updates
    • investigating · Nov 10, 2026, 10:05 AM UTC

      We are doing an emergency maintenance on https://app.prismacloud.io/ , some of the services might see degraded performance Maintenance Window : 3:00AM-4:00AM , PST

    • resolved · Nov 10, 2026, 12:16 PM UTC

      Maintenance completed successfully.

    Latest: Maintenance completed successfully.

  2. Resolved 7d 5h
    Started Nov 09, 2026, 11:45 AM UTC · Resolved Nov 16, 2026, 04:51 PM UTC
    Americas - US - app.prismacloud.ioAmericas - US - app2.prismacloud.ioAmericas - US - app3.prismacloud.ioAmericas - US - app4.prismacloud.ioAmericas - US - app.gov.prismacloud.ioAmericas - Canada - app.ca.prismacloud.ioEurope - app.eu.prismacloud.ioEurope - app2.eu.prismacloud.ioUnited Kingdom - UK - app.uk.prismacloud.ioFrance - FR - app.fr.prismacloud.io
    Timeline · 44 updates
    • investigating · Nov 09, 2026, 11:45 AM UTC

      We are currently investigating this issue.

    • identified · Nov 09, 2026, 11:59 AM UTC

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

    • identified · Nov 09, 2026, 03:04 PM UTC

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

    • identified · Nov 09, 2026, 04:18 PM UTC

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

    • identified · Nov 09, 2026, 05:18 PM UTC

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

    • identified · Nov 09, 2026, 06:15 PM UTC

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

    • identified · Nov 09, 2026, 07:15 PM UTC

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

    • identified · Nov 09, 2026, 08:18 PM UTC

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

    • identified · Nov 09, 2026, 09:15 PM UTC

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

    • identified · Nov 09, 2026, 10:22 PM UTC

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

    • identified · Nov 09, 2026, 11:16 PM UTC

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

    • identified · Nov 10, 2026, 12:15 AM UTC

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

    • identified · Nov 10, 2026, 01:09 AM UTC

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

    • identified · Nov 10, 2026, 04:55 AM UTC

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

    • identified · Nov 10, 2026, 10:07 AM UTC

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

    • identified · Nov 10, 2026, 01:05 PM UTC

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

    • identified · Nov 10, 2026, 03:43 PM UTC

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

    • identified · Nov 10, 2026, 04:55 PM UTC

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

    • identified · Nov 10, 2026, 05:45 PM UTC

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

    • identified · Nov 10, 2026, 06:46 PM UTC

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

    • identified · Nov 10, 2026, 07:45 PM UTC

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

    • identified · Nov 10, 2026, 08:45 PM UTC

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

    • identified · Nov 10, 2026, 09:52 PM UTC

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

    • identified · Nov 10, 2026, 10:45 PM UTC

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

    • identified · Nov 10, 2026, 11:45 PM UTC

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

    • identified · Nov 11, 2026, 12:45 AM UTC

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

    • identified · Nov 11, 2026, 01:45 AM UTC

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

    • identified · Nov 11, 2026, 02:45 AM UTC

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

    • identified · Nov 11, 2026, 03:55 PM UTC

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

    • identified · Nov 11, 2026, 05:03 PM UTC

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

    • identified · Nov 11, 2026, 07:40 PM UTC

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

    • identified · Nov 11, 2026, 09:05 PM UTC

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

    • identified · Nov 11, 2026, 10:00 PM UTC

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

    • identified · Nov 11, 2026, 11:14 PM UTC

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

    • identified · Nov 12, 2026, 03:54 PM UTC

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

    • identified · Nov 12, 2026, 05:22 PM UTC

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

    • identified · Nov 12, 2026, 06:30 PM UTC

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

    • identified · Nov 12, 2026, 07:44 PM UTC

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

    • identified · Nov 12, 2026, 08:56 PM UTC

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

    • identified · Nov 13, 2026, 05:42 PM UTC

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

    • identified · Nov 13, 2026, 07:43 PM UTC

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

    • identified · Nov 13, 2026, 09:01 PM UTC

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

    • identified · Nov 15, 2026, 11:14 PM UTC

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

    • resolved · Nov 16, 2026, 04:51 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 57m
    Started Nov 04, 2026, 10:58 PM UTC · Resolved Nov 04, 2026, 11:55 PM UTC
    France
    Timeline · 1 update
    • investigating · Nov 04, 2026, 10:58 PM UTC

      We have a scheduled maintenance for File Manager (FileMgr) in France region. The maintenance is scheduled for November 4th 2026 from 23:00 to November 5th 01:00 UTC. Customers may encounter intermittent disconnections during the maintenance window.

    Latest: We have a scheduled maintenance for File Manager (FileMgr) in France region. The maintenance is scheduled for November 4th 2026 from 23:00 to November 5th 01:00 UTC. Customers may …

  4. Resolved 4h 55m
    Started Oct 30, 2026, 05:36 AM UTC · Resolved Oct 30, 2026, 10:32 AM UTC
    Americas - US - app.prismacloud.ioAmericas - US - app2.prismacloud.ioAmericas - US - app3.prismacloud.ioAmericas - US - app4.prismacloud.ioAmericas - US - app.gov.prismacloud.ioAmericas - Canada - app.ca.prismacloud.ioEurope - app.eu.prismacloud.ioEurope - app2.eu.prismacloud.ioUnited Kingdom - UK - app.uk.prismacloud.ioFrance - FR - app.fr.prismacloud.io
    Timeline · 3 updates
    • identified · Oct 30, 2026, 05:36 AM UTC

      We are experiencing delayed Alibaba cloud ingestion across all the stacks. We have identified the issue and a fix is being rolled out.

    • identified · Oct 30, 2026, 09:02 AM UTC

      Services have been restored across app, app2, app3, and app4. Restoration of the remaining stacks is currently in progress.

    • resolved · Oct 30, 2026, 10:32 AM UTC

      The services are restored in all the stacks.

    Latest: The services are restored in all the stacks.

  5. Resolved 1h 52m
    Started Oct 26, 2026, 04:40 PM UTC · Resolved Oct 26, 2026, 06:33 PM UTC
    DLP (NGFW) NAMPrisma Access DLP
    Timeline · 3 updates
    • identified · Oct 26, 2026, 04:40 PM UTC

      We are experiencing higher than normal latency in our US West region. We have identified the issue and are working on a fix.

    • monitoring · Oct 26, 2026, 05:09 PM UTC

      A fix has been deployed and we are seeing recovery. We will continue to monitor the situation and provide updates on progress.

    • resolved · Oct 26, 2026, 06:33 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Palo Alto Networks outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Palo Alto Networks outage history →

Or sign up free to get alerts when Palo Alto Networks breaks · 3 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 531 components checked every 5 minutes
112incidents recorded
112last 12 months
22last 90 days
3 daystypical duration, 12 months

The longest incident in the last year, AWS Middle East(Bahrain) outage impacting Cloud NGFW Services. on March 2, 2026, ran for 233 days. 950 maintenance windows announced in the same period.

How Palo Alto Networks compares

Palo Alto Networks reported more incidents in the last 12 months than 554 of the 570 other Security services Pingoru tracks. The typical one reported 5. Its incidents typically last 3 days; across Security services the typical figure is 7 hours. Counts come from each vendor's own status page, so a vendor that reports openly can show more incidents than one that does not.

How quickly Palo Alto Networks posts incidents

Palo Alto Networks posts incidents promptly: 96% of the 52 Pingoru saw in the last 12 months appeared on its status page within 15 minutes of the start time Palo Alto Networks gave them. Pingoru checks every 5 minutes, so a gap can read up to 5 minutes longer than the vendor's own delay.

Platforms Palo Alto Networks names in its incidents

In the last 12 months Palo Alto Networks named these platforms in the titles of its own incidents.

Most affected components, last 12 months

  • Americas - US - app3.prismacloud.io9
  • westus38
  • centralus7
  • westus27
  • United States - Americas6

Latest incidents

Outage history

Past 90 days · 22 incidents· showing the latest 9 View full outage history →