Akamai: edge failed
Akamai was partly broken for 5 minutes on 22 Oct 2026.
Measured by trying the real thing every five minutes from Sydney, Virginia and Frankfurt.
Sydneysaw edge fail
FailedVirginiadid not see it fail
PassedFrankfurtdid not see it fail
PassedWhat happened
Opened
Closed
Lasted5 minutes
Stepedge
CitiesSydney
Closed after two consecutive clean windows, which is how this network avoids opening ten incidents for one flapping service.
The screen we saw
No screenshot for this one. The capture is not switched on yet: it needs a screenshot-only job on the walk fleet, and that code is frozen while P49's clock runs.
What Akamai says
“All Systems Operational”
On Akamai's status page, read 57 minutes ago.
That is their line now, not a quote from the time: we store the latest reading only, and a timestamped quote we never kept would be an invention.
On their page: Customer Security Advisory: PHP Remote Code Execution Vulnerabilities
Akamai's status page: “We are continuing to assess the reported vulnerabilities (CVE-2026-109618 and CVE-2026-10961) across our systems and applications. Our initial assessment has identified systems and applications that may be affected, and remediation efforts, including patching, are actively underway.At this time, we have found no evidence indicating that these vulnerabilities have impacted our products, API calls, or Control Center. We will continue to review our systems and applications to assess potential exposure and identify any additional remediation requirements.Mitigation efforts are being prioritized b…”Investigating
Akamai's status page: “Update - We are continuing to assess the reported vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our systems and applications. Our initial assessment has identified systems and applications that may be affected, and remediation efforts, including patching, are actively underway.At this time, we have found no evidence indicating that these vulnerabilities have impacted our products, API calls, or Control Center. We will continue to review our systems and applications to assess potential exposure and identify any additional remediation requirements. Mitigation efforts are being pr…”Identified
Akamai's status page: “We can confirm that remediation efforts for the reported vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were completed as of 20:06 UTC on October 23, 2026.We have found no evidence that these vulnerabilities impacted Akamai products, API calls, or Control Center. Customers and partners can view additional details by logging in to Control Center or contacting Akamai Support.We apologize for any concern this advisory may have caused and thank you for your patience and continued support. We remain committed to improving our systems and reducing the risk of similar issues in the future.”Resolved
Akamai's status page: “Customers and partners can find an incident summary report, here: [https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC](https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC)”Postmortem
On their page: Web Security Analytics, Reporting and Configuration Deployment Issues
Akamai's status page: “We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.”Identified
Akamai's status page: “We have rolled back a release that we believe may have caused this issue as of 16:42 UTC on October 21, 2026; based on current observations, the service is resuming normal operations. Additional issues related to Configuration Deployment are related to https://www.akamaistatus.com/incidents/p7jmyq5fhbfh. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will continue to monitor to ensure that the impact has been fully mitigated.”Monitoring
Akamai's status page: “We can confirm that the issue was mitigated at 20:45 UTC on October 21, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.”Resolved
Akamai's status page: “Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK”Postmortem
On their page: Edge Delivery Secure CDN platform at Risk of Capacity Issues
Akamai's status page: “We continue to work on implementing a permanent fix to prevent recurrence. We can confirm that there are currently no delivery issues and that the network has remained stable since the brief impact observed at approximately 18:23 UTC. Additionally, as of 20:09 UTC, our propagation system channels are processing requests normally.We will provide our next update during the US business day on October 22.”Identified
Akamai's status page: “We continue to work on implementing a permanent fix to prevent recurrence. The deployment with the fix is continuing with no issues and it is expected to finalize tomorrow October 23rd during US business hours. During this time customers may experience minor instability; however, we do not anticipate any service disruptions. We are closely monitoring our systems and the deployment to ensure that there is no impact during this period.We will provide our next update during the US business day on October 23rd.”Identified
Akamai's status page: “We can confirm that the issue was mitigated at 17:44 UTC on October 23, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.17:”Resolved
Akamai's status page: “Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0”Postmortem
Was your store affected?
If you sell through Akamai, this is the window to check. Bilby will walk your store now, try to buy something, and show you the screen where it stopped. Free.
Check my store free
