Prisma Cloud's asset inventory on app3 served stale data for nearly two days on 29 September 2026. The fault sat in Palo Alto Networks' own backend processing, not in reachability, which is why nothing about the service going down showed up externally.
Started
06:32 UTC
Duration
Lasted 1d 22h
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 - app3.prismacloud.io
What happened?
Palo Alto Networks' status page logged one incident on 29 September 2026, affecting the component "Americas - US - app3.prismacloud.io". It started at 06:32 UTC under the title "PrismaCloud: APP3: Stale data in asset inventory" and ran for 46h 54m before being marked resolved at 05:25 UTC two days later. The first update, posted at the start, said the issue had been identified and a fix was being implemented. A second update at 09:36 UTC simply said work on the fix was continuing, with no detail on what the fix involved or why it was taking this long. The final update, at 05:25 UTC, closed the incident with a single line: "This incident has been resolved." That is three updates total across nearly two full days, and no post-mortem has been published to explain what caused the stale data or why remediation took as long as it did. The component list names only app3 in the Americas region, so this looks like a regional data-freshness problem rather than a global Prisma Cloud failure. No user reports were filed during the window on this page's record. Palo Alto Networks' own history for the past 90 days shows 22 incidents with a median duration of 6 hours 43 minutes, so a 46h 54m incident is well outside the norm for this provider.
Learning
UptimeRobot's own probes against the prisma component, across EU and NA regions, held 100% uptime over the past 24 hours, 7 days and 30 days, and this incident was not registered against those checks. That is not a contradiction. Stale asset inventory data is a backend processing fault: the API endpoint keeps responding, authentication keeps working, and every external check that pings for a response comes back green, while the actual data your dashboards and security tooling pull from Prisma Cloud is out of date. An uptime probe tests whether the door opens, not whether what is behind it is current. If your product depends on Prisma Cloud's asset inventory being fresh, a clean uptime report from your own monitoring tells you nothing about whether the data feeding your decisions is accurate. This is the kind of failure that only shows up on the vendor's own status page, because the fault lives entirely on their side of the handshake. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
