Vendor reports: degradedResolved · vendor status “resolved”Official status API

Log forwarding and streaming degradation for Device Security Cloud Service

Reported by Palo Alto Networks · Identity & Security · source last read just now

Vendor start
Aug 19, 2026, 22:59 UTC
Vendor's clock
Resolved
Aug 21, 2026, 18:35 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 19 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Palo Alto Networks reports degraded: "Log forwarding and streaming degradation for Device Security Cloud Service".[E1, E2]
  • The vendor marked it resolved at 2026-08-21 18:35 UTC.[E3, E7]

Affected products and regions

  • Components: United States.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-21 18:35 UTC · summary s1, evidence 958b2982b43efbca

Evidence (7)
  1. E1Palo Alto Networks reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Log forwarding and streaming degradation for Device Security Cloud Service". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-08-19 22:59 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: United States. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-21 18:35 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: United States

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Palo Alto Networks is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Aug 19, 2026, 22:59 UTCVendor-reported startVendor time
  2. Aug 21, 2026, 18:35 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.