Akamai Status

Monitoring: We will continue to monitor to ensure that the impact has been fully mitigated. Further updates will be provided as we make progress.

Monitoring: 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.

Investigating: 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: 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/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

Resolved: Akamai has completed its investigation of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479). We have not identified any impact to Akamai’s platform or infrastructure, and services remain operating normally.If you run a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, follow F5/NGINX guidance and apply the available patches.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, or by reaching out to Akamai Support. Thank you for your patience and continued support.

Monitoring: 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://www.akamai.com/us/en/support/.

Monitoring: 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. We will update the affected components as our investigation progresses.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://www.akamai.com/us/en/support/.

Identified: 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 Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

Investigating: 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 NGINX Plus, we recommend following guidance from F5/NGINX and applying available patches.We will post more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications as additional information becomes available. If you have questions or are experiencing an impact due 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://www.akamai.com/us/en/support/.

Resolved: Our investigation revealed that a significant majority of the Akamai Platform is not subject to the MPTCP attack vector for this vulnerability. Remediation efforts for any other externally exposed and vulnerable systems have been completed as well. Customers and partners can find more details on the Akamai Community:https://community.akamai.com/customers/s/feed/0D5a700001cIGoWCAW or by reaching out to Akamai Support. We remain committed to improving our systems and reducing the risk of similar issues in the future.

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/0D5a700001cIGoWCAW. We will provide an update as we progress.

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/0D5a700001cIGoWCAW. We will provide an update as we progress. 

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/0D5a700001cIGoWCAW. We will provide an update as we progress.

Investigating: 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 Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

Resolved: We can confirm that the issue was mitigated at 17:15 UTC on November 2, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.

Investigating: 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 Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.