Palo Alto Networks favicon

Palo Alto Networks outage on 2026-11-10

paloaltonetworks.com
November 2026 10 Minor incident

Prisma Cloud's app.prismacloud.io was marked as affected for 2h 14m on 10 November 2026 after Palo Alto Networks ran emergency maintenance on the US North Virginia instance. The company scheduled and ran the window itself, so this was a planned action by the provider rather than an unplanned fault.

Started

10:05 UTC

Duration

Lasted 2h 14m

Source

IsDown

Next time

Palo Alto Networks is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Americas - US - app.prismacloud.io

What happened?

The only incident logged for the day affected a single component: Americas - US - app.prismacloud.io. The status page entry was titled "Emergency maintenance on app.prismacloud.io ( US - North Virginia ) 3AM-4AM, PST" and opened at 10:05 UTC, with the first update warning that some services might see degraded performance during a 3:00AM-4:00AM PST window. Palo Alto Networks closed it at 12:16 UTC with a single line: "Maintenance completed successfully." That is the entire record, two updates covering a 2h 14m span, with no breakdown of which services degraded or how badly. No user reports were filed during the window, so there is no independent account of what, if anything, you or anyone else actually experienced on the app. Over the past 90 days Palo Alto Networks has logged 24 incidents on this service with a median duration of 3 hours 22 minutes, so this one ran shorter than typical. Across all time the company has filed 1,485 incidents at a rate of roughly 22.2 a month, which is a high volume of status page activity for this product line. UptimeRobot's own probes against the Prisma component, run every 60 seconds from EU and NA regions, recorded 100% uptime over 24 hours and over 7 days, and 99.982% over 30 days. The probes were not registered against this specific incident. Over the last 30 days UptimeRobot logged 10 incidents of its own against this service, with 9 resolved, and a median duration of 2h 14m, matching this one almost exactly.

Learning

This was maintenance, announced in advance by Palo Alto Networks itself, and that is a different animal from an unplanned fault. A scheduled window that degrades performance for some services can sail straight past an external uptime check if the check's specific path or region happens to stay responsive, which is consistent with UptimeRobot's probes reading 100% uptime across 24 hours and 7 days while the vendor's own status page carried an open incident for 2h 14m. Neither reading is wrong. The probes tell you the monitored endpoint answered correctly from outside, the vendor's notice tells you they were deliberately touching infrastructure that could affect some users and not others. If your own dashboards looked clean during this window, that is expected, because your monitoring watches your integration, not Palo Alto Networks' maintenance calendar. The gap is exactly the kind of thing that catches people out when they assume a quiet dashboard means a quiet provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.