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

Delayed Alibaba cloud ingestion for all customers

Reported by Palo Alto Networks · Identity & Security · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Oct 30, 2026, 05:36 UTC
Vendor's clock
Resolved
Oct 30, 2026, 10:32 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
4 h 56 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: "Delayed Alibaba cloud ingestion for all customers".[E1, E2]
  • The vendor marked it resolved at 2026-10-30 10:32 UTC.[E3, E7]

Affected products and regions

  • 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, United Kingdom - UK - app.uk.prismacloud.io, France - FR - app.fr.prismacloud.io, China - app.prismacloud.cn, Asia Pacific - Singapore - app.sg.prismacloud.io, Asia Pacific - India - app.ind.prismacloud.io, Asia Pacific - Japan - app.jp.prismacloud.io, Asia Pacific - Australia - app.anz.prismacloud.io, Asia Pacific - Indonesia - app.id.prismacloud.io.[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-10-30 10:32 UTC · summary s1, evidence 3f3ad8d8da7443a2

Evidence (7)
  1. E1Palo Alto Networks reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Delayed Alibaba cloud ingestion for all customers". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-30 05:36 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: 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, United Kingdom - UK - app.uk.prismacloud.io, France - FR - app.fr.prismacloud.io, China - app.prismacloud.cn, Asia Pacific - Singapore - app.sg.prismacloud.io, Asia Pacific - India - app.ind.prismacloud.io, Asia Pacific - Japan - app.jp.prismacloud.io, Asia Pacific - Australia - app.anz.prismacloud.io, Asia Pacific - Indonesia - app.id.prismacloud.io. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-30 10:32 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

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, United Kingdom - UK - app.uk.prismacloud.io, France - FR - app.fr.prismacloud.io, China - app.prismacloud.cn, Asia Pacific - Singapore - app.sg.prismacloud.io, Asia Pacific - India - app.ind.prismacloud.io, Asia Pacific - Japan - app.jp.prismacloud.io, Asia Pacific - Australia - app.anz.prismacloud.io, Asia Pacific - Indonesia - app.id.prismacloud.io

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. Oct 30, 2026, 05:36 UTCVendor-reported startVendor time
  2. Oct 30, 2026, 10:32 UTCVendor-reported resolutionVendor time

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