Akamai Outage History

Started Jul 27, 2026, 01:46 AM UTC· resolved Jul 27, 2026, 06:07 AM UTC

1. investigating Jul 27, 2026, 01:46 AM UTC

   We are investigating an issue with Bot Manager related to false positive issues with availability. 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/.

2. monitoring Jul 27, 2026, 02:11 AM UTC

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

3. resolved Jul 27, 2026, 06:07 AM UTC

   We can confirm that the issue was mitigated at 01:30 UTC on 27 July 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/0D5a700001Kh1F0CAJ 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.

Read the full incident report →

Started Jul 19, 2026, 07:40 AM UTC· resolved Jul 20, 2026, 02:46 PM UTC

1. investigating Jul 19, 2026, 07:40 AM UTC

   We are investigating an issue with Edge Delivery where users may have experienced delivery errors and connection time outs. The issue is not occurring at this time. We are actively investigating the cause and will provide the details of the investigation as we make progress. 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/.

2. investigating Jul 19, 2026, 11:06 AM UTC

   We are continuing to investigate the cause. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001JVmHpCAL We will provide an update as we make progress.

3. monitoring Jul 19, 2026, 01:58 PM UTC

   The third-party service provider has identified the cause of the issue and implemented a fix as of 04:10 UTC on July 19, 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/0D5a700001JVmHpCAL. We will continue to monitor to ensure that the impact has been fully mitigated.

4. resolved Jul 20, 2026, 02:46 PM UTC

   We can confirm that the issue was mitigated at 04:10 UTC on July 19, 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/0D5a700001JVmHpCAL 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.

Read the full incident report →

Started Jul 02, 2026, 02:40 PM UTC· resolved Jul 06, 2026, 04:11 AM UTC

1. investigating Jul 02, 2026, 02:40 PM UTC

   We are investigating an emerging issue with Edge Delivery involving timeouts and performance degradation in the Pakistan region. 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/.

2. investigating Jul 02, 2026, 03:05 PM UTC

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

3. investigating Jul 02, 2026, 03:34 PM UTC

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

4. identified Jul 02, 2026, 05:51 PM UTC

   The issue has been identified as related to a submarine cable issue affecting traffic to/from Pakistan. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GuST3CAN. We will provide an update as we progress.

5. monitoring Jul 02, 2026, 09:42 PM UTC

   We have implemented network changes to route traffic away from the affected areas while the ISP continues to work on the submarine cable issue; based on current observations, the service has resumed normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GuST3CAN. We will continue to monitor to ensure that the impact has been fully mitigated.

6. resolved Jul 06, 2026, 04:11 AM UTC

   We can confirm that the issue was mitigated at 4:20 UTC on July 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.

Read the full incident report →

Started Jun 30, 2026, 09:15 PM UTC· resolved Jun 30, 2026, 10:02 PM UTC

1. investigating Jun 30, 2026, 09:15 PM UTC

   We are investigating an emerging issue with Akamai Control Center related to Property Manager issues, where users may experience errors when trying to activate new properties or perform changes to their properties related to EdgeWorkers. 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/feed/0D5a700001GabcKCAR. 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/.

2. identified Jun 30, 2026, 09:23 PM UTC

   We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai https://community.akamai.com/customers/s/feed/0D5a700001GabcKCAR. We will provide an update within the next 60 minutes.

3. resolved Jun 30, 2026, 10:02 PM UTC

   We can confirm that the issue was mitigated at 21:14 UTC on June 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/0D5a700001GabcKCAR 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.

Read the full incident report →

Started Jun 28, 2026, 02:45 PM UTC· resolved Jun 29, 2026, 03:42 PM UTC

1. investigating Jun 28, 2026, 02:45 PM UTC

   We are investigating an emerging issue with Cloudlets related to issues while activating Application Load Balancing configurations. 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/feed/0D5a700001GB7HRCA1. 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/.

2. investigating Jun 28, 2026, 03:10 PM UTC

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

3. investigating Jun 28, 2026, 03:57 PM UTC

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

4. monitoring Jun 28, 2026, 05:22 PM UTC

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

5. monitoring Jun 29, 2026, 12:42 AM UTC

   We are continuing to monitor for any further issues; 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/0D5a700001GB7HRCA1. We will continue to monitor to ensure that the impact has been fully mitigated.

6. resolved Jun 29, 2026, 03:42 PM UTC

   We can confirm that the issue was mitigated at 16:50 UTC on June 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/0D5a700001GB7HRCA1 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.

Read the full incident report →

Started Jun 25, 2026, 06:14 PM UTC· resolved Jun 26, 2026, 11:35 PM UTC

1. investigating Jun 25, 2026, 06:14 PM UTC

   We are investigating an emerging issue with DataStream related to configuring and editing DataStream configurations with users possibly running into the following errors: "There are no eligible properties available to clone the stream.", "One or more properties are invalid. Provide properties that are authorized to be a part of this stream, and belong to the contract and group ID.". 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/.

2. investigating Jun 25, 2026, 06:58 PM UTC

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

3. investigating Jun 25, 2026, 07:54 PM UTC

   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/0D5a700001FiyHGCAZ. Subsequent updates around mitigation status will be posted as progress is made.

4. monitoring Jun 25, 2026, 09:59 PM UTC

   We have rolled back a release which we believe may have caused this issue as of 20:55 UTC on 25 June 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/0D5a700001FiyHGCAZ. We will continue to monitor to ensure that the impact has been fully mitigated.

5. monitoring Jun 26, 2026, 12:45 AM UTC

   We are actively monitoring the fix for this issue and will share updates on mitigation status as progress continues. Thank you for your patience.

6. resolved Jun 26, 2026, 11:35 PM UTC

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

Read the full incident report →

Started Jun 16, 2026, 01:37 PM UTC· resolved Jun 16, 2026, 02:20 PM UTC

1. resolved Jun 16, 2026, 03:45 PM UTC

   We became aware of an issue with HTTP and HTTPS related to latency and performance degradation while accessing the applications. The issue lasted between 13:37 UTC and 14:20 UTC on June 16, 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/0D5a700001E6lLpCAJ 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.

Read the full incident report →

Started Jun 12, 2026, 10:00 AM UTC· resolved Jun 12, 2026, 09:00 PM UTC

1. resolved Jun 12, 2026, 02:58 PM UTC

   We identified an issue with the Datastream service where between 10:00 UTC and 21:00 UTC on June 11, 2026, customers may have experienced degraded fidelity on CDN observability streams. We can confirm that the issue is now mitigated as of 21:00 UTC on June 11, 2026, and no longer occurring. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001DVkdgCAD. We apologize for any impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.

Read the full incident report →

Started Jun 10, 2026, 06:38 PM UTC· resolved Jun 11, 2026, 04:41 PM UTC

1. investigating Jun 10, 2026, 06:38 PM UTC

   We are investigating an emerging issue with Bot Manager Premier related to some legitimate users utilizing a specific rule to be denied. 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/

2. monitoring Jun 10, 2026, 06:51 PM UTC

   We have implemented a fix for this issue as of 18:41 UTC on June 10, 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/0D5a700001D7uShCAJ. We will continue to monitor to ensure that the impact has been fully mitigated.

3. resolved Jun 11, 2026, 04:41 PM UTC

   We can confirm that the issue was mitigated at 18:41 UTC on June 10, 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/0D5a700001D7uShCAJ 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.

Read the full incident report →

Started Jun 06, 2026, 04:29 AM UTC· resolved Jun 06, 2026, 07:21 AM UTC

1. investigating Jun 06, 2026, 04:29 AM UTC

   We became aware of an issue with Edge Delivery in Americas Region related to elevated packet loss and service degradation between 1:00 UTC and 1:30 UTC on June 6, 2026. We are actively investigating the cause of the elevated packet loss within the affected environment and assessing customer impact. At this time, the issue appears to have stabilized, and we will continue to monitor the platform closely. We will provide additional updates as we make further progress in our investigation. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001CQ6lqCAD.

2. resolved Jun 06, 2026, 07:21 AM UTC

   We can confirm that the issue was mitigated at 1:30 UTC on June 6, 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/0D5a700001CQ6lqCAD 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.

Read the full incident report →

Started Jun 05, 2026, 04:16 PM UTC· resolved Jun 19, 2026, 11:07 AM UTC

1. investigating Jun 05, 2026, 04:16 PM UTC

   We are investigating an emerging issue with HTTP Edge IP binding related to API timeouts and transaction failures. 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/.

2. investigating Jun 05, 2026, 04:36 PM UTC

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

3. investigating Jun 08, 2026, 07:56 PM UTC

   The further updates regarding this issue will be provided at https://www.akamaistatus.com/incidents/nxwt5pz35k0cWe are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015iVQMCA2 We will provide an update as we progress.

4. investigating Jun 11, 2026, 06:54 PM UTC

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

5. resolved Jun 19, 2026, 11:07 AM UTC

   We can confirm that the issue was mitigated at 17:30 UTC on June 12, 2026, 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/0D5a7000015iVQMCA2, 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.

Read the full incident report →

Started May 21, 2026, 01:58 PM UTC· resolved May 21, 2026, 04:52 PM UTC

1. investigating May 21, 2026, 01:58 PM UTC

   We are investigating an emerging issue with Email Exchange server related to delay with the emails. 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/.

2. identified May 21, 2026, 02:00 PM UTC

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

3. monitoring May 21, 2026, 02:04 PM UTC

   We have implemented a fix for this issue as of 13:00 UTC on May 21, 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/0D5a7000019St8yCACWe will continue to monitor to ensure that the impact has been fully mitigated.

4. resolved May 21, 2026, 04:52 PM UTC

   We can confirm that the issue was mitigated at 14:50 UTC on May 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/0D5a7000019St8yCAC 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.

Read the full incident report →

Started May 20, 2026, 02:29 PM UTC· resolved May 21, 2026, 12:36 PM UTC

1. investigating May 20, 2026, 02:29 PM UTC

   We are investigating an emerging issue with Configuration Deployment related to EdgeWorkers and mPulse configuration activations. 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/.

2. identified May 20, 2026, 02:50 PM UTC

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

3. identified May 20, 2026, 03:18 PM UTC

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

4. identified May 20, 2026, 03:37 PM UTC

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

5. identified May 20, 2026, 03:55 PM UTC

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

6. identified May 20, 2026, 04:16 PM UTC

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

7. identified May 20, 2026, 04:36 PM UTC

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

8. identified May 20, 2026, 05:02 PM UTC

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

9. identified May 20, 2026, 05:28 PM UTC

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

10. identified May 20, 2026, 05:53 PM UTC

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

11. identified May 20, 2026, 06:17 PM UTC

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

12. identified May 20, 2026, 06:45 PM UTC

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

13. identified May 20, 2026, 07:09 PM UTC

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

14. identified May 20, 2026, 07:35 PM UTC

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

15. identified May 20, 2026, 08:00 PM UTC

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

16. monitoring May 20, 2026, 08:25 PM UTC

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

17. monitoring May 20, 2026, 11:23 PM UTC

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

18. resolved May 21, 2026, 12:36 PM UTC

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

19. postmortem May 25, 2026, 11:08 PM UTC

    Starting around 12:00 UTC on May 20, 2026, users experienced difficulties with configuration deployments for mPulse and EdgeWorkers. During this period, activations within Property Manager were impacted, preventing affected customers from successfully updating or deploying these configurations. Akamai initiated an investigation and determined that the issue was caused by a tripped circuit breaker, which resulted in multiple racks in the data center losing power. We responded with a series of coordinated actions to address both the immediate power outage and its downstream effects on critical services. At 14:45 UTC on May 20, 2026, a failover was completed, and by 14:55 UTC on May 20, 2026, error rates in the Akamai Control Center began to decrease, and the issue was mitigated. We will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact. We appreciate your patience as we worked to resolve this issue. If you have further questions, please post them on [https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS](https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS). This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Started May 19, 2026, 10:13 AM UTC· resolved Jun 01, 2026, 07:46 AM UTC

1. identified May 19, 2026, 10:13 AM UTC

   We are aware of an issue with the 'URL Traffic' and ‘URL Responses’ report related to reporting data unavailability. We have identified the cause of the issue, and a fix is being implemented. 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 the Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

2. identified May 20, 2026, 08:07 AM UTC

   The data is slowly getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.

3. identified May 22, 2026, 05:20 AM UTC

   The data is getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.

4. monitoring May 28, 2026, 09:50 AM UTC

   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/0D5a7000018q2TuCAI. We will continue to monitor to ensure that the impact has been fully mitigated.

5. resolved Jun 01, 2026, 07:46 AM UTC

   We can confirm that the issue was mitigated 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/0D5a7000018q2TuCAI 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.

Read the full incident report →

Started May 14, 2026, 06:08 PM UTC· resolved May 14, 2026, 06:45 PM UTC

1. investigating May 14, 2026, 06:08 PM UTC

   We are investigating an emerging issue with Cloudlets related to issues with activating Cloudlets policies. 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/.

2. identified May 14, 2026, 06:28 PM UTC

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

3. monitoring May 14, 2026, 06:37 PM UTC

   We have rolled back a release which we believe may have caused this issue as of 18:21 UTC on May 14th, 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/0D5a70000189Hk3CAE. We will continue to monitor to ensure that the impact has been fully mitigated.

4. resolved May 14, 2026, 06:45 PM UTC

   We can confirm that the issue was mitigated at 18:21 UTC on May 14th, 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/0D5a70000189Hk3CAE, 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.

Read the full incident report →

Started May 13, 2026, 09:33 AM UTC· resolved May 13, 2026, 10:25 AM UTC

1. investigating May 13, 2026, 09:33 AM UTC

   We are investigating an emerging issue with Edge Delivery related to general performance degratation in Amsterdam, Netherlands. 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/.

2. resolved May 13, 2026, 10:25 AM UTC

   We can confirm that the issue was mitigated at approximately 09:40 UTC on May 13, 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/0D5a7000017tokVCAQ 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.

Read the full incident report →

Started May 12, 2026, 05:08 PM UTC· resolved May 13, 2026, 01:08 AM UTC

1. investigating May 12, 2026, 05:08 PM UTC

   We are investigating an emerging issue with a third-party service provider, causing performance degradation with Edge Delivery between India and Europe. We are working with the service provider and 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, or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

2. investigating May 12, 2026, 05:29 PM UTC

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

3. investigating May 12, 2026, 06:39 PM UTC

   We are continuing to 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/0D5a7000017mjDUCAY. We will provide an update within the next 120 minutes.

4. identified May 12, 2026, 07:50 PM UTC

   Our third-party service provider has 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/0D5a7000017mjDUCAY. Subsequent updates around mitigation status will be posted as progress is made.

5. investigating May 12, 2026, 10:44 PM UTC

   We are continuing to work with our third-party service provider to mitigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY. Subsequent updates around mitigation status will be posted as progress is made.

6. resolved May 13, 2026, 01:08 AM UTC

   We can confirm that the issue was mitigated at 00:25 UTC on May 13, 2026 and the service has resumed normal operation. While we continue to monitor the upstream provider's progress on their underlying connectivity issue, our services are now stable on alternative paths. Customers and partners can view additional details about the incident by logging in to https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY or reaching out to Akamai Support. We thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.

7. postmortem May 14, 2026, 03:15 PM UTC

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

Read the full incident report →

Started Apr 30, 2026, 06:41 PM UTC· resolved Apr 30, 2026, 08:00 PM UTC

1. investigating Apr 30, 2026, 06:41 PM UTC

   We are investigating an emerging issue with Bot Manager related to elevated false positives leading to denied legitimate traffic for end users. 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/.

2. monitoring Apr 30, 2026, 07:02 PM UTC

   We have implemented a fix for Bot Manager which addresses the issue we believe may have caused the elevated false positives as of 19:00 UTC on April 30, 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/0D5a70000168PJsCAM. We will continue to monitor to ensure that the impact has been fully mitigated.

3. resolved Apr 30, 2026, 08:00 PM UTC

   We can confirm that the issue was mitigated at 19:00 UTC on April 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/0D5a70000168PJsCAM, 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.

Read the full incident report →

Started Apr 28, 2026, 04:42 PM UTC· resolved May 04, 2026, 03:05 AM UTC

1. investigating Apr 28, 2026, 04:42 PM UTC

   We have identified an issue with a network resource failure in the MAA (Chennai, IN) region related to intermittent delays and timeouts during peak traffic hours with Delivery and other Akamai services that traverse into/through the MAA region. We are actively investigating opportunities to increase network capacity in the region while working to replace the failed resource as quickly as possible. An update will be provided in 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/.

2. identified Apr 28, 2026, 05:44 PM UTC

   We are continuing to work to identify opportunities for increasing capacity in the Chennai, IN (MAA) region to prevent issues during peak traffic hours. The current ETA for the hardware replacement effort is end of day on April 29, 2026. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015jW2OCAU. We will provide an update as we progress.

3. identified Apr 28, 2026, 09:02 PM UTC

   We have optimized capacity in the Chennai, IN (MAA) region to the best of our abilities. At this time there is no degradation to services in the region, but we do expect that intermittent delays and timeouts for Edge Delivery and other services such as Bot Manager Premier may arise during peak traffic hours in the region until we can replace the degraded hardware. Current ETA for hardware replacement continues to be end of day on April 29, 2026. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015jW2OCAU. We will provide an update as progress is made.

4. identified Apr 29, 2026, 10:13 PM UTC

   We were able to identify a solution which resulted in additional capacity for the Chennai, IN region and did not experience any degradation over the peak hours on April 29, 2026. The replacement of the network component has been briefly delayed. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015jW2OCAU. We will provide an update as progress is made.

5. resolved May 04, 2026, 03:05 AM UTC

   We can confirm that the issue was mitigated at 12:00 UTC on 2 May, 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/0D5a7000015jW2OCAU 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.

Read the full incident report →

Started Apr 28, 2026, 02:50 AM UTC· resolved Apr 28, 2026, 05:02 PM UTC

1. investigating Apr 28, 2026, 02:50 AM UTC

   We have identified an issue with Traffic Reports where users may stop seeing data for "Traffic by Hostname" post 23:00 UTC on April 27, 2026. We are actively working with the appropriate Subject Matter Experts to mitigate the issue. We apologize for the impact. We will provide an update in 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/.

2. investigating Apr 28, 2026, 03:41 AM UTC

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

3. investigating Apr 28, 2026, 04:38 AM UTC

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

4. investigating Apr 28, 2026, 05:33 AM UTC

   We are continuing to investigate this issue and our SMEs have determined the potential cause. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015dBomCAEWe will provide another update as we make progress.

5. monitoring Apr 28, 2026, 07:18 AM UTC

   The delay in reports is determined to be due to a runtime memory issue. This has been addressed at around 4:30 UTC on April 28, 2026. Customers and partners can find more details on the Akamai Community:https://community.akamai.com/customers/s/feed/0D5a7000015dBomCAE . We will continue to monitor to ensure that the impact has been fully mitigated.

6. resolved Apr 28, 2026, 05:02 PM UTC

   We can confirm that the issue was mitigated at 13:30 UTC on April 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/0D5a7000015dBomCAE 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.

Read the full incident report →

Started Apr 27, 2026, 03:20 AM UTC· resolved Apr 27, 2026, 01:27 PM UTC

1. investigating Apr 27, 2026, 03:20 AM UTC

   We are investigating an issue with Secure Internet Access related to access issues with certificate 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 the Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

2. investigating Apr 27, 2026, 03:58 AM UTC

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

3. monitoring Apr 27, 2026, 05:44 AM UTC

   We have implemented a fix for this issue as of 05:26 UTC on 27 April 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/0D5a7000015Qwi8CAC. We will continue to monitor to ensure that the impact has been fully mitigated.

4. resolved Apr 27, 2026, 01:27 PM UTC

   We can confirm that the issue was mitigated at 05:26 UTC on 27 April, 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/0D5a7000015Qwi8CAC 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.

Read the full incident report →

Started Apr 24, 2026, 08:07 PM UTC· resolved Apr 24, 2026, 11:52 PM UTC

1. investigating Apr 24, 2026, 08:07 PM UTC

   We are investigating an emerging issue with TrafficPeak related to timeout errors experienced across panels. 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/.

2. identified Apr 24, 2026, 08:34 PM UTC

   We have identified a potential 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/0D5a7000015H7xxCAC?language=en_US. We will provide an update within the next 60 minutes.

3. identified Apr 24, 2026, 09:30 PM UTC

   We are continuing work to apply the identified fix. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015H7xxCAC?language=en_US. We will provide an update within the next 60 minutes.

4. identified Apr 24, 2026, 10:06 PM UTC

   We are continuing work to apply the identified fix. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015H7xxCAC?language=en_US. We will provide an update within the next 60 minutes.

5. identified Apr 24, 2026, 11:07 PM UTC

   We are continuing work to apply the identified fix. We will provide an update within the next 60 minutes.

6. resolved Apr 24, 2026, 11:52 PM UTC

   We can confirm that the issue was mitigated at 23:36 UTC on April 24, 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/0D5a7000015H7xxCAC?language=en_US 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.

Read the full incident report →

Started Apr 23, 2026, 02:11 PM UTC· resolved Apr 28, 2026, 05:39 PM UTC

1. investigating Apr 23, 2026, 02:11 PM UTC

   We are investigating an emerging issue with WSA where incomplete or missing data is reported when filtering by TLS v3 Fingerprint. 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/.

2. investigating Apr 23, 2026, 03:06 PM UTC

   We are continuing to work with our subject matter experts to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a70000151eEnCAIWe will provide an update within the next 60 minutes.

3. investigating Apr 23, 2026, 03:56 PM UTC

   We are continuing to work with our subject matter experts to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notificationsWe will provide an update within the next 120 minutes.

4. investigating Apr 23, 2026, 06:19 PM UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notificationsWe will provide an update within the next 3 hours.

5. investigating Apr 23, 2026, 09:50 PM UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notifications. Subsequent updates around mitigation status will be posted as progress is made.

6. resolved Apr 28, 2026, 05:39 PM UTC

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

Read the full incident report →

Started Apr 23, 2026, 09:44 AM UTC· resolved Apr 23, 2026, 09:44 AM UTC

1. resolved Apr 23, 2026, 09:44 AM UTC

   We became aware of an issue in the Akamai Control Center related to errors when using the "Translate Error String" tool within "Edge Diagnostics". The issue lasted between 20:34 UTC on April 22, 2026, and 8:31 UTC on April 23, 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/0D5a7000014zYTlCAM 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.

Read the full incident report →

Started Apr 20, 2026, 12:25 PM UTC· resolved Apr 21, 2026, 01:07 AM UTC

1. investigating Apr 20, 2026, 12:25 PM UTC

   We are investigating an emerging issue with edge delivery in our Frankfurt (DE-FRA-2) Data Center where customers may experience performance degradation. 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/.

2. investigating Apr 20, 2026, 12:58 PM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 20, 2026, 01:54 PM UTC

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

4. resolved Apr 21, 2026, 01:07 AM UTC

   We can confirm that the issue was mitigated at 13:12 UTC on April 20, 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.

5. postmortem Apr 21, 2026, 02:18 PM UTC

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

Read the full incident report →