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

AWS EU-NORTH-1 (Stockholm) disruption impacting Cloud NGFW

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

Official source (opens in a new tab)
Vendor start
Jun 30, 2026, 21:30 UTC
Vendor's clock
Resolved
Jun 30, 2026, 22:04 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
34 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 degraded: "AWS EU-NORTH-1 (Stockholm) disruption impacting Cloud NGFW".[E1, E2]
  • The vendor marked it resolved at 2026-06-30 22:04 UTC.[E3, E7]

Affected products and regions

  • Regions: eu-north-1 (read from the title, so inferred).[E5]
  • Components: Stockholm (eu-north-1).[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-06-30 22:04 UTC · summary s1, evidence 685e55d442a1d2c0

Evidence (7)
  1. E1Palo Alto Networks reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "AWS EU-NORTH-1 (Stockholm) disruption impacting Cloud NGFW". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-06-30 21:30 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): eu-north-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Stockholm (eu-north-1). (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-06-30 22:04 UTC. (vendor) source (opens in a new tab)

Affected scope

eu-north-1

Components: Stockholm (eu-north-1)

Read from region codes written in the incident title, so treat it as inferred.

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. Jun 30, 2026, 21:30 UTCVendor-reported startVendor time
  2. Jun 30, 2026, 22:04 UTCVendor-reported resolutionVendor time

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