Akamai favicon

Akamai outage on 2026-10-21

akamaistatus.com
October 2026 21 Minor incident

On 21 October 2026, Akamai ran four separate incidents touching NetStorage, Configuration Deployment, Reporting, Web Security Analytics and Edge Delivery. The longest ran 53h 16m, and the fault sat with Akamai's own systems, not with anything on your side.

Started

14:52 UTC

Duration

Lasted 9h 20m

Source

IsDown

Next time

Akamai is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Edge Delivery, Configuration Deployment, Web Security Analytics, Reporting, NetStorage

What happened?

Akamai logged four incidents starting between 14:52 and 18:59 UTC on 21 October. The first was a NetStorage problem in the Los Angeles area, described as performance degradation and timeouts, lasting 9h 20m and mitigated at roughly 22:00 UTC. The second was a security advisory about two PHP remote code execution CVEs, open for 53h 16m, which Akamai closed by saying it found no evidence the vulnerabilities actually affected its products, API calls or Control Center. The third combined Web Security Analytics, Reporting and Configuration Deployment, running 32h 25m, where Akamai said WSA and Reporting were working as expected partway through but Configuration Deployments kept sitting in a "pending" state longer than usual; Akamai rolled back a release it believed caused the issue and later confirmed mitigation at 20:45 UTC on 21 October. The fourth was an Edge Delivery problem affecting the Secure CDN platform's capacity, lasting 48h 1m, where Akamai reported a brief impact around 18:23 UTC followed by a longer deployment of a permanent fix that finished during US business hours on 23 October, with Akamai warning of possible minor instability but no further service disruption expected. Akamai's status page carries 23 updates across the four incidents. No user reports were filed during the window. Akamai's own notes are the only account of impact here, and they vary in how specific they get: the NetStorage and Configuration Deployment incidents name a time of mitigation, the security advisory ends with a finding of no actual impact, and the Edge Delivery incident stretches over two days with a rollback and a scheduled fix window in between.

Learning

UptimeRobot's own probes, checking edge reachability from both the EU and North America every 60 seconds, read 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was never registered against them. That is not a contradiction. Akamai's incidents here were about NetStorage timeouts in one region, configuration deployments queuing up, a CDN capacity risk and a vulnerability advisory, none of which necessarily shows up as a simple failed reachability check from outside. A control plane can be degraded, a deployment pipeline can be backed up, and a security team can be working through a CVE, while the edge itself keeps answering requests normally. This is the general shape worth recognising: the layer that broke was often behind the delivery path, not on it, so watching your own endpoints would not have caught it. Akamai's 90 day history shows 31 incidents with a median duration of 19 hours 52 minutes, so a multi-day run like this one is not unusual for this provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.