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

WildFire Issue

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

Official source (opens in a new tab)
Vendor start
Aug 11, 2026, 11:06 UTC
Vendor's clock
Resolved
Aug 11, 2026, 12:09 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 4 min
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 operational: "WildFire Issue".[E1, E2]
  • The vendor marked it resolved at 2026-08-11 12:09 UTC.[E3, E7]

Affected products and regions

  • Components: WildFire Global Cloud, WildFire Europe Cloud, WildFire Singapore Cloud, WildFire Japan Cloud, WildFire UK Cloud, WildFire U.S. Government Cloud, WildFire Canada Cloud, WildFire Australia Cloud, WildFire Germany Cloud, WildFire India Cloud, WildFire Switzerland Cloud, WildFire Poland Cloud, WildFire Indonesia Cloud, WildFire Taiwan Cloud, WildFire France Cloud, WildFire Qatar Cloud, WildFire South Korea Cloud, WildFire Israel Cloud, WildFire Saudi Arabia Cloud, WildFire Italy Cloud, Wildfire Spain Cloud, WildFire AWF PubSec Cloud(FRM), WildFire AWF GovCloud(FRH), WildFire South Africa Cloud, WildFire EU Regulated Cloud, WildFire GVS Cloud, WildFire US Native Cloud, WildFire Delhi Cloud, WildFire Brazil Cloud, WildFire Finland Cloud, WildFire EU Sovereign Cloud.[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-11 12:09 UTC · summary s1, evidence 1860370e57dd6f9d

Evidence (7)
  1. E1Palo Alto Networks reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "WildFire Issue". (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-11 11:06 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: WildFire Global Cloud, WildFire Europe Cloud, WildFire Singapore Cloud, WildFire Japan Cloud, WildFire UK Cloud, WildFire U.S. Government Cloud, WildFire Canada Cloud, WildFire Australia Cloud, WildFire Germany Cloud, WildFire India Cloud, WildFire Switzerland Cloud, WildFire Poland Cloud, WildFire Indonesia Cloud, WildFire Taiwan Cloud, WildFire France Cloud, WildFire Qatar Cloud, WildFire South Korea Cloud, WildFire Israel Cloud, WildFire Saudi Arabia Cloud, WildFire Italy Cloud, Wildfire Spain Cloud, WildFire AWF PubSec Cloud(FRM), WildFire AWF GovCloud(FRH), WildFire South Africa Cloud, WildFire EU Regulated Cloud, WildFire GVS Cloud, WildFire US Native Cloud, WildFire Delhi Cloud, WildFire Brazil Cloud, WildFire Finland Cloud, WildFire EU Sovereign Cloud. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-08-11 12:09 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: WildFire Global Cloud, WildFire Europe Cloud, WildFire Singapore Cloud, WildFire Japan Cloud, WildFire UK Cloud, WildFire U.S. Government Cloud, WildFire Canada Cloud, WildFire Australia Cloud, WildFire Germany Cloud, WildFire India Cloud, WildFire Switzerland Cloud, WildFire Poland Cloud, WildFire Indonesia Cloud, WildFire Taiwan Cloud, WildFire France Cloud, WildFire Qatar Cloud, WildFire South Korea Cloud, WildFire Israel Cloud, WildFire Saudi Arabia Cloud, WildFire Italy Cloud, Wildfire Spain Cloud, WildFire AWF PubSec Cloud(FRM), WildFire AWF GovCloud(FRH), WildFire South Africa Cloud, WildFire EU Regulated Cloud, WildFire GVS Cloud, WildFire US Native Cloud, WildFire Delhi Cloud, WildFire Brazil Cloud, WildFire Finland Cloud, WildFire EU Sovereign Cloud

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 11, 2026, 11:06 UTCVendor-reported startVendor time
  2. Aug 11, 2026, 12:09 UTCVendor-reported resolutionVendor time

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