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

Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

Reported by Akamai · Hosting, CDN & Edge · source last read just now

Official source (opens in a new tab)
Vendor start
Oct 22, 2026, 20:17 UTC
Vendor's clock
Resolved
Nov 10, 2026, 18:03 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
18 d 21 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

  • Akamai reports operational: "Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities".[E1, E2]
  • The vendor marked it resolved at 2026-11-10 18:03 UTC.[E3, E7]

Affected products and regions

  • Components: Customer Security Advisory.[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-11-10 18:03 UTC · summary s1, evidence 62c1877fc8b7be6f

Evidence (7)
  1. E1Akamai reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities". (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-22 20:17 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Customer Security Advisory. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-11-10 18:03 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Customer Security Advisory

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Akamai 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 22, 2026, 20:17 UTCVendor-reported startVendor time
  2. Nov 10, 2026, 18:03 UTCVendor-reported resolutionVendor time

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