On 23 October, Akamai opened an advisory for a remote code execution vulnerability in Brotli decoding, tracked as CVE-2026-111497, rather than a service outage. The advisory has stayed open since 12:00 UTC with no resolution filed, and Akamai says it has so far found no evidence of customer impact.
Started
12:00 UTC
Duration
Lasted 11d 5h
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.
What happened?
Akamai's status page opened this advisory at 12:00 UTC on 23 October for CVE-2026-111497, a remote code execution vulnerability tied to Brotli decompression. This is a security advisory, not a report of a platform component going down, and Akamai's own updates treat it that way throughout. The first update said subject matter experts were investigating and taking mitigation actions while monitoring the platform. By 20:07 UTC, Akamai wrote that it had not found evidence of customer impact caused by the vulnerability, and it repeated that line again at 00:34 UTC the next day. At 16:13 UTC on the following update, Akamai said the scope of the CVE had been expanded to cover any foreign data processed with the Brotli decoder, not just node.js, widening the set of systems under review. By 17:43 UTC, Akamai reported that a significant majority of its platform was not affected and that investigation continued into the remaining products. Seven updates have been posted in total, all carrying a status of investigating or identified, and none have closed the advisory out. Akamai has pointed customers and partners to its community forum for further detail rather than publishing a full technical breakdown on the status page itself. No components are listed as affected in Akamai's own tracker, and no user reports were filed during the window covered here. The advisory remains open, with 16:13 UTC and 17:43 UTC being the last two substantive updates on the record.
Learning
This advisory is a case where the right comparison is not between what Akamai said and what your monitoring saw, because the two are answering different questions. UptimeRobot's own probes against Akamai's edge reachability, checked every 60 seconds across EU and NA regions, show 100% uptime over the past 24 hours, 7 days and 30 days, and this incident was never registered against those checks. That is expected: a vulnerability disclosure about a decoding library is not the same thing as edge nodes failing to respond, and Akamai itself says it has not found evidence of customer impact. The lesson here is not about outage detection but about advisory tracking. A status page entry that stays in "investigating" for days, widens its own scope mid-stream, and never resolves is a signal worth watching even when nothing turns red on an uptime check. If your product touches Brotli decoding anywhere in its stack, this is the kind of filing you want flagged regardless of whether your probes ever move. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.