Akamai: edge failed
Akamai was partly broken for 5 minutes on 9 Nov 2026.
Measured by trying the real thing every five minutes from Sydney, Virginia and Frankfurt.
Sydneydid not see it fail
PassedVirginiadid not see it fail
PassedFrankfurtsaw edge fail
FailedWhat happened
Opened
Closed
Lasted5 minutes
Stepedge
CitiesFrankfurt
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: Critical F5/NGINX Out-of-Band Vulnerabilities
Akamai's status page: “Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are investigating their potential impact across our platform and infrastructure.F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed.If you are running a vulnerable version of NGINX Open Source or NG…”Investigating
Akamai's status page: “Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Our teams are taking action where necessary and will provide additional updates as more information becomes available.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact related to this issue, please use the Support Center on Aka…”Identified
Akamai's status page: “Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure.As part of our initial assessment, we included EAA, MFA, and SIA in the affected component selection. Based on our investigation to date, we have determined that these offerings are not vulnerable to these CVEs and have updated the affected component selection accordingly. We apologize for any concern this may have caused.Our teams continue to monitor the situation closely and respond where necessary…”Monitoring
Akamai's status page: “Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https…”Monitoring
On their page: Edge Delivery issues between Indonesia and Singapore
Akamai's status page: “We are investigating an emerging issue with Edge delivery related to performance degradation and timeouts between Indonesia and Singapore. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/s…”Investigating
Akamai's status page: “We are continuing to work with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001b6aheCAA. Subsequent updates around mitigation status will be posted as progress is made.”Investigating
Akamai's status page: “We have implemented a fix for this issue as of 13:11 UTC on 25 October, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001b6aheCAA. We will continue to monitor to ensure that the impact has been fully mitigated.”Monitoring
Akamai's status page: “We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.”Monitoring
On their page: Performance Degradation for Customers in Mumbai and Chennai
Akamai's status page: “On October 27, 2026, between 08:05 UTC and 10:45 UTC customers using services in Mumbai and Chennai may have experienced performance degradation. This occurred due to packet loss within an upstream provider’s network. As of 10:45 UTC the loss has subsided, and we are no longer seeing degraded performance in the affected regions. We have been monitoring for recurrence, and will continue to do so for the next few hours.If you have questions or are still experiencing an impact due to this issue, please use the Support Center on Akamai Community, or Akamai Control Center, to contact Akamai Techni…”Investigating
On their page: Customer Security Advisory: CVE-2026-98432
Akamai's status page: “Akamai is aware of the recently published remote code execution CVE-2026-98432. We are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control…”Investigating
Akamai's status page: “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/0D5a700001cIGoWCAW. We will provide an update as we progress.”Investigating
Akamai's status page: “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/0D5a700001cIGoWCAW. We will provide an update as we progress. ”Investigating
Akamai's status page: “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/0D5a700001cIGoWCAW. We will provide an update as we progress.”Investigating
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
