Akamai outage history

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/.

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.

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.

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.

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.

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.

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.

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.

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.

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/.

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/.

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/.

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/.

We are investigating an emerging issue with our Secure CDN platform with risk of impacting capacity. We are actively investigating the issue and will provide another update within the next 30 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/.

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/0D5a700001aSoWGCA0. We will provide an update within the next 60 minutes.

We are continuing to investigate this issue. We will provide an update within the next 60 minutes.

We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0. We will continue to provide updates as progress is made.

We have identified the cause of the issue, and a fix is being implemented. We will continue to provide updates as progress is made.

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.

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.

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:

Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0

We are investigating an emerging issue with Web Security Application, Reporting, and Configuration Deployment related to latency and errors. We are actively investigating the issue and will provide another update within the next 30 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/.

We have identified the cause of the issue, and a fix is being implemented. 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 30 minutes.

Based on our observations, WSA and Reporting are working as expected. Configuration Deployments are experiencing higher latency and may take longer in the "pending" state than usual. However, these configurations will eventually be deployed to production after a longer-than-usual delay. 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.

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.

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.

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.

Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK

Akamai is aware of the recently published remote code execution vulnerabilities CVE-2026-109618 and CVE-2026-10961). Our subject matter experts are actively investigating and taking the appropriate measures. We have released security updates to address these CVEs and monitor for exploitation attempts. We are actively monitoring our platform while we perform the mitigation actions. 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/.

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 based on the assessment of potential risk and impact. We remain focused on addressing identified vulnerabilities and will provide further updates as additional information becomes available. We will provide further updates as we make progress.

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 prioritized based on the assessment of potential risk and impact. We remain focused on addressing identified vulnerabilities and will provide further updates as additional information becomes available. We will provide further updates as we make progress.

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.

We are investigating an emerging issue with NetStorage related to performance degradation and timeouts in the Los Angeles area. 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/.

We continue investigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aOfDBCA0. We will provide an update within the next 120 minutes.

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

We can confirm that the issue was mitigated at approximately 22:00 UTC on 21 October 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/0D5a700001aOfDBCA0 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.

We are investigating an emerging issue with Edge Delivery related to Edge DNS report with record change on master DNS server not reflected to Akamai Edge DNS. We are actively investigating the issue and will provide another update within the next 30 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/.

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

We can confirm that the issue was mitigated at 14:45 UTC on October 2, 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/0D5a700001WrkrnCAB 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.

We became aware of an issue with Configuration Deployment and Akamai Control Center related to errors when activating delivery configurations in Property Manager and an inability to access Identity Manager in Akamai Control Center to manage users. The issue lasted between 14:13 UTC and 14:34 UTC on September 30, 2026. We can confirm that the issue is now resolved, 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/0D5a700001WM3dyCAD 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.

We are investigating an emerging issue with Configuration Deployment related to errors while activating delivery configurations in Property Manager. We are actively investigating the issue and will provide another update within the next 30 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/.

We are continuing to investigate the issue. We identified another issue in Identity Manager where customers can't access to manage their users in Akamai Control Center. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001WM3dyCAD. We will provide an update within the next 60 minutes.

We can confirm that the issue was mitigated at 20:25 UTC on September 29, 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/0D5a700001WM3dyCAD 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.

We are investigating an emerging issue in Canada with Edge Delivery related to performance degradation with 0xx error. We are actively investigating the issue and will provide another update within the next 30 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/.

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

Our third-party service provider has confirmed that the issue was mitigated at 16:08 UTC on September 28, 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/0D5a700001W3hnvCAB 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.

We are investigating an emerging issue with Account Protector. We are actively investigating the issue and will provide another update within the next 30 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/.

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/0D5a700001VNuHQCA1. We will provide an update within the next 60 minutes.

We are continuing to investigate this issue. We will provide an update within the next 60 minutes.

We have implemented a fix for this issue as of 22:45 UTC on September 23, 2026; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.

We can confirm that the issue was mitigated at 22:45 UTC on September 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/0D5a700001VNuHQCA1 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.

We became aware of an issue with origin server connectivity that caused intermittent connectivity issues and elevated errors for some customers in affected regions. The issue was resolved at approximately 11:41 UTC on 22 September, 2026. The issue appears to have self-corrected; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure the impact has been fully mitigated. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to help prevent a recurrence of this issue.

We have identified that this issue was likely due to upstream congestion related to unexpected maintenance on subsea cables. The impact was primarily observed when requests from outside the APAC region were routed to origins in the APAC region, and when requests from the APAC region were routed to origins outside the region. We are working with the upstream ISP(s) to gather additional details.Based on our 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/0D5a700001V5RQqCAN. We will continue to monitor to ensure the impact has been fully mitigated.

We are continuing to monitor to ensure the impact has been fully mitigated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN

Our upstream carrier continues to work on the maintenance of the impacted subsea cables. Although immediate impact has subsided, customers may still experience intermittent impact until the repair works are completed - the current estimate points to early October, 2026, subject to change. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN. We will continue to monitor to ensure that the impact has been fully mitigated.

We can confirm that the issue was mitigated at 11:41 UTC on 22 September 2026, and the service has resumed normal operation. We have not observed any related impact to the Akamai platform since the issue self-corrected.We remain in contact with our upstream providers and continue to monitor the related repair work for this incident. Customers and partners can view additional details by logging in to the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN or by contacting Akamai Support.We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to help prevent recurrence.

Scheduled upstream provider maintenance is currently taking place along network routes connecting Singapore, Hong Kong, and Japan from September 18, 2026 at 06:30 UTC through October 3, 2026 at 23:59 UTC. While core service remains operational, customers in the affected regions may notice increased latency during peak traffic hours. We are monitoring network performance until maintenance concludes.Customers and partners with a valid Control Center login can find updates 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/.

We will continue to monitor the network performance until the maintenance concludes. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V0be8CAB. We will provide the next update as we make progress.

We can confirm that the issue was mitigated on September 30, 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/0D5a700001V0be8CAB 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.

We are investigating an emerging issue with a third-party service provider where users might experience issues creating new tickets with Akamai Support. The issue appears to have started around 08:00 UTC on Sep 16, 2026. The customers can use https://control.akamai.com/apps/support-ui/#/contact-support or reach out to country-specific support numbers for urgent cases. We are working with the service provider and actively investigating the issue and will provide another update within the next 60 minutes.

We are continuing to work 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/0D5a700001U5jVxCAJ.

The third-party provider has implemented a fix for this issue as of 12:20 UTC on 16 Sep,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/0D5a700001U5jVxCAJ. We will continue to monitor to ensure that the impact has been fully mitigated

We can confirm that the issue was mitigated at 12:20 UTC on Sep 16, 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/0D5a700001U5jVxCAJ 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.

We became aware of an issue with the HTTPS edge delivery network related to performance issues. The issue lasted between 00:45 UTC and 00:57 UTC on 15 September 2026. We have implemented a fix for this issue, which we believe may have caused the issue; 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/0D5a700001TpkinCAB. We will continue to monitor to ensure that the impact has been fully mitigated. 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.

We are continuing to monitor the issue to ensure that the impact is fully mitigated. We will provide the next update as we make progress. We apologize for the impact.

We can confirm that the issue was mitigated at 00:57 UTC on 15 September 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/0D5a700001TpkinCAB 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.

We are investigating an emerging issue with Edge Delivery related to increased latency and elevated end user 403 errors. 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/.

We have identified the cause of the issue and are implementing a fix. We initially mentioned elevated 403 errors in this status page post as an additional symptom of the incident. That was incorrect, and we have removed the reference. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001T8d9uCAB. We will provide another update within the next 60 minutes.

We have implemented a fix for this issue as of 18:10 UTC on 10 September 2026; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.

We can confirm that the issue was mitigated at 00:10 UTC on 11 September 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/0D5a700001T8d9uCAB 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.

We became aware of an issue with a network component related to connectivity in the Atlanta, GA region which impacted the Certificate Provisioning System as well as potential impact to other Edge traffic through the region. The issue lasted between 12:21 UTC and 14:19 UTC on September 4, 2026. We can confirm that the issue is now resolved, 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.

We are investigating an issue with Application Load Balancer (ALB) reporting related to availability with errors. 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/feed/0D5a700001S7tYbCAJ . 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/.

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/0D5a700001S7tYbCAJ. We will provide the next update as we make progress.

We have implemented a fix for this issue as of 14:20 UTC on 4 September, 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/0D5a700001S7tYbCAJ. We will continue to monitor to ensure that the impact has been fully mitigated.

We can confirm that the issue was mitigated at 14:20 UTC on 4 September, 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/0D5a700001S7tYbCAJ 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.

We are investigating an issue with Event Center related to the reporting dashboard being inaccessible with data unavailability. 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/feed/0D5a700001QvOI6CAN. 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/.

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/0D5a700001QvOI6CAN. We will provide the next update as we make progress.

We have implemented a fix for this issue as of 03:30 UTC on 28 August 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/0D5a700001QvOI6CAN. We will continue to monitor to ensure that the impact has been fully mitigated.

We can confirm that the issue was mitigated at 03:30 UTC on 28 August 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/0D5a700001QvOI6CAN 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.