- Level
- confirmed
- Worst impact
- Operational
- Components
- Akamai Customer Community
What to do
Check whether you use Akamai Akamai Customer Community. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 11d 5h it lasted.
Anything that failed between 2026-10-23 12:00 UTC and 2026-11-03 17:13 UTC may need a replay.Subscribe to Akamai's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=akamai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Akamai 8
- investigating
Akamai is aware of the recently published remote code execution vulnerability: CVE-2026-111497.Our subject matter experts are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. We will provide updates as additional information becomes available.In the interest of time, we are providing you with the most current information available, which is subject to changes, corrections, and updates.
provider
- investigating
We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAIWe will provide an update as we progress.
provider
- investigating
We are continuing to investigate this issue to evaluate any possible impact to customers and our platform, so far we don't have evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.
provider
- identified
We will continue to investigate and evaluate any possible impact to customers and our platform over the weekend. So far the investigation has not shown evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.
provider
- investigating
We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAI We will provide subsequent updates as we make progress.
provider
- investigating
We are continuing to investigate this issue. The scope of this CVE has been expanded to include any foreign data which is being processed with the Brotli decoder, not just node.js. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAIWe will provide an update as we progress.
provider
- investigating
Our investigation has revealed that a significant majority of our Platform is not affected by this CVE. We are continuing to investigate this issue to evaluate possible impact to customers and remaining Akamai products. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAI. We will provide an update as we progress.
provider
- resolved
As of November 2, 2026, at approximately 23:00 UTC, we completed all platform hardening measures to fully mitigate Akamai's potential exposure to the Brotli Remote Code Execution vulnerability (CVE-2026-111497). All systems are secured, and we have detected no evidence of unauthorized access or impact to customer environments.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-699fb46251
Is Akamai still down?
No, this incident was resolved 2026-11-03 17:13 UTC. For Akamai's live state, see https://down.guide/akamai.
How long did it last?
11d 5h, from 2026-10-23 12:00 UTC to 2026-11-03 17:13 UTC, by the times Akamai posted.
What was affected?
Akamai named Akamai Customer Community.
What caused it?
Akamai hasn't published a root cause. If it does, it shows here.
Where does this come from?
Akamai's official status page, https://www.akamaistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.