Prisma Cloud's Alert Manual and Automated Remediation feature went down on 9 November, affecting eleven components across every region Palo Alto Networks lists for Prisma Cloud. The fault sat on Palo Alto Networks' side and the incident shows as resolved after 173h 10m, which is the duration the record gives verbatim.
Started
11:45 UTC
Duration
Lasted 7d 5h
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, Americas - US - app2.prismacloud.io, Americas - US - app3.prismacloud.io, Americas - US - app4.prismacloud.io, Americas - US - app.gov.prismacloud.io, Americas - Canada - app.ca.prismacloud.io, Europe - app.eu.prismacloud.io, Europe - app2.eu.prismacloud.io, Asia Pacific - Australia - app.anz.prismacloud.io, Asia Pacific - Singapore - app.sg.prismacloud.io, China - app.prismacloud.cn
What happened?
Palo Alto Networks' status page opened this incident at 11:45 UTC, flagging that Alert Manual and Automated Remediation was unavailable in Prisma Cloud. The affected component list spans eleven entries, covering app.prismacloud.io and its numbered variants in the Americas, the government instance, the Canadian instance, both European apps, Australia, Singapore and the China instance. That spread points to a shared remediation backend rather than a single regional front end, since the symptom hit nearly every geography Palo Alto Networks runs Prisma Cloud in. Fourteen minutes after opening, at 11:59 UTC, the status page moved to "identified" and said a fix was being implemented. At 15:04 UTC the only substantive update of the day repeated that work on a fix was continuing, with no detail on what the fix involved. The incident was marked resolved at 16:51 UTC. The total time from first post to resolution shown on the record is 173h 10m. That span does not match the roughly five-hour gap between the posted timestamps, and Palo Alto Networks has not published anything explaining the discrepancy, so the longer figure is what the record carries and is printed here without adjustment. No post-mortem has been filed beyond the four updates logged. No user reports were filed during this window, so there is nothing from outside Palo Alto Networks' own page to cross-check against. Over the past 90 days Palo Alto Networks has logged 23 incidents with a median duration of 3 hours 22 minutes, which makes this one run well past the typical length for this provider.
Learning
UptimeRobot's own probes watched the Prisma Cloud component across the EU and North America regions through this window and recorded 100% uptime at 24 hours, 7 days and 30 days, with this incident not registered against that monitoring. That is not a contradiction. The affected feature, automated and manual remediation of alerts, is a backend processing path inside Prisma Cloud, not the reachability of the app endpoint itself, so an external check hitting the app URL can return a clean result while the remediation workflow behind it stays broken. This is the general shape of failures that live inside a vendor's processing layer rather than its front door: the page loads, the login works, but a specific job queue or automation path is stalled, and nothing external will show it. If your product depends on Prisma Cloud's automated remediation firing on schedule, your own uptime checks against the app would have told you nothing was wrong while alerts sat unprocessed for days. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.