Palo Alto Networks' Enterprise DLP service ran with elevated latency in the US West region for 1h 56m on 26 October 2026. The fault sat on Palo Alto Networks' side, inside the Prisma Access DLP and DLP (NGFW) NAM components.
Started
16:40 UTC
Duration
Lasted 1h 56m
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: Prisma Access DLP, DLP (NGFW) NAM
What happened?
Palo Alto Networks logged one incident on this day, affecting two components: Prisma Access DLP and DLP (NGFW) NAM. It started at 16:40 UTC, when the vendor reported higher than normal latency in its US West region and said it had already identified the cause. At 17:09 UTC it posted that a fix had been deployed and recovery was underway, then marked the incident resolved at 18:33 UTC, putting the total length at 1h 56m. That is three updates across just under two hours, which is a thin trail for anyone trying to work out exactly what failed inside the DLP pipeline. The vendor's own text never names a root cause beyond "higher than normal latency," so what triggered it is not on the record. No user reports were filed during this window, so there is no independent account of what the latency looked like from outside Palo Alto Networks' own monitoring. Over the past 90 days Palo Alto Networks has logged 25 incidents with a median duration of 3 hours 40 minutes, so this one ran shorter than typical for this vendor. Across all time the company has logged 1,481 incidents at a pace of about 22.4 a month, which gives useful context for how often this kind of filing appears versus how long any single one usually runs.
Learning
UptimeRobot's own probes against the Prisma component, run from EU and NA regions every 60 seconds, stayed at 100% uptime over 24 hours and 7 days, and 99.982% over 30 days, with this incident not registering as a hit against those checks. That is not a contradiction. A regional latency problem inside a vendor's DLP processing pipeline can sit entirely behind the API surface that external probes reach, so a probe can return clean while real traffic through that pipeline is slower than normal. This is the shape worth remembering: your own endpoint checks tell you whether your product is reachable, not whether every internal queue or region on your provider's side is running at normal speed. Over the last 30 days UptimeRobot recorded 10 incidents against this provider, all resolved, with a median duration of 2h 19m, which gives you a baseline for how long these latency events tend to run even when they never touch your own uptime numbers. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.