Live / Akamai / Incident
Akamai: Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
Akamai · akamai.comResolved2026-11-10 18:03 UTC
Public — what happened
Summary
Akamai said it began looking into three newly published security flaws in F5's NGINX web server software on 2026-10-22, to see whether its own platform and infrastructure were affected. On 2026-10-23 it said three offerings (EAA, MFA and SIA) had been listed as possibly affected in error, since they were found not to be vulnerable. On 2026-11-10 Akamai said it had finished its investigation, found no impact to its platform or infrastructure, and that services were operating normally. It advised customers running a vulnerable NGINX version on a Linode instance to follow F5/NGINX guidance and install the available patches.
Affected
Customer Security Advisory
Timeline
- Started — 2026-10-22 20:17 UTC
- Investigating — 2026-10-22 20:17 UTC
- Identified — 2026-10-23 17:18 UTC
- Monitoring — 2026-10-23 20:03 UTC (2 updates)
- Resolved — 2026-11-10 18:03 UTC · 19 days after it started
What SquidGrid measured
SquidGrid measured 252 internet paths into Akamai’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Akamai against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Akamai: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Akamai report →
More from Akamai
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.