Akamai Outage History

Started Apr 16, 2026, 03:17 AM UTC· resolved Apr 16, 2026, 06:44 AM UTC

1. investigating Apr 16, 2026, 03:17 AM UTC

   We are investigating an issue with NetStorage related to issues with new storage group creations or making changes to the existing storage groups. 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 Apr 16, 2026, 03:45 AM 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/0D5a7000013s3OVCAY. We will provide the next update as we make progress.

3. monitoring Apr 16, 2026, 06:09 AM UTC

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

4. resolved Apr 16, 2026, 06:44 AM UTC

   We can confirm that the issue was mitigated at 04:57 UTC on 16 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/0D5a7000013s3OVCAY 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 07, 2026, 12:11 PM UTC· resolved Apr 14, 2026, 07:47 PM UTC

1. investigating Apr 07, 2026, 12:11 PM UTC

   We are investigating an emerging issue with Data Services related to Reporting specifically with "Traffic by Geography" and "URL Traffic" where data is missing after March 28, 2026. 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 Apr 07, 2026, 12:31 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/0D5a7000012RCWbCAO We will provide an update as we progress.

3. identified Apr 07, 2026, 07: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/0D5a7000012RCWbCAO We will provide an update as we progress.

4. identified Apr 08, 2026, 09:45 AM UTC

   We are continuing to work toward mitigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012RCWbCAO We will provide an update as we progress.

5. identified Apr 09, 2026, 06:31 PM UTC

   We are continuing to work toward mitigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012RCWbCAO We will provide an update as we progress.

6. monitoring Apr 13, 2026, 02:14 PM UTC

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

7. resolved Apr 14, 2026, 07:47 PM UTC

   We can confirm that the issue was mitigated at 11:00 UTC on April 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/0D5a7000012RCWbCAO 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 07, 2026, 10:02 AM UTC· resolved Apr 07, 2026, 01:31 PM UTC

1. investigating Apr 07, 2026, 10:02 AM UTC

   We are investigating an emerging issue with the Certificate Provisioning System related to users being presented with errors while trying to access the application via Akamai Control Center. 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 07, 2026, 10:36 AM UTC

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

3. resolved Apr 07, 2026, 01:31 PM UTC

   We can confirm that the issue was mitigated at 9:49 UTC on April 7, 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/0D5a7000012QbOsCAK 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 06, 2026, 06:22 PM UTC· resolved Apr 15, 2026, 04:02 PM UTC

1. investigating Apr 06, 2026, 06:22 PM UTC

   We are investigating an emerging issue with Edge Delivery related to packet loss and general 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 06, 2026, 06: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/0D5a7000012K6RECA0. We will provide an update within the next 60 minutes.

3. monitoring Apr 06, 2026, 07:46 PM UTC

   We have implemented a fix for this issue as of approximately 18:30 UTC on April 6, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012K6RECA0. We will continue to monitor to ensure that the impact has been fully mitigated.

4. monitoring Apr 06, 2026, 10:54 PM UTC

   We are continuing to monitor the situation following temporary mitigations put in place to restore service stability. While performance has stabilized, we will continue to provide periodic updates until a permanent mitigation has been fully implemented. Customers and partners can find additional technical details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012K6RECA0.

5. monitoring Apr 08, 2026, 11:53 PM UTC

   We are continuing to monitor the situation in the Chicago, Illinois region following the implementation of permanent mitigations. Service performance remains stable, and our monitoring indicates there is minimal impact to customers at this time. We will provide further updates as needed to ensure the issue remains fully resolved. Customers and partners can find additional technical details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012K6RECA0.

6. resolved Apr 15, 2026, 04:02 PM UTC

   We can confirm that the issue was mitigated at 23:12 UTC on April 10, 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 Apr 03, 2026, 04:54 AM UTC· resolved Apr 06, 2026, 09:55 AM UTC

1. investigating Apr 03, 2026, 04:54 AM UTC

   We are investigating an issue with Cloudlets related to activation failures. 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 03, 2026, 05:13 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/0D5a7000011usZNCAY. We will provide the next update as we make progress.

3. investigating Apr 03, 2026, 08:24 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/0D5a7000011usZNCAY. We will provide an update as we make progress.

4. investigating Apr 03, 2026, 10:27 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/0D5a7000011usZNCAY. We will provide an update as we make progress.

5. monitoring Apr 03, 2026, 12:00 PM UTC

   We have rolled back a change which we believe may have caused this issue as of approximately 11:30 UTC on April 3, 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/0D5a7000011usZNCAY. We will continue to monitor to ensure that the impact has been fully mitigated.

6. resolved Apr 06, 2026, 09:55 AM UTC

   We can confirm that the issue was mitigated at 11:29 UTC on 3 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/0D5a7000011usZNCAY 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.

7. postmortem Apr 07, 2026, 01:19 AM UTC

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

Read the full incident report →

Started Mar 31, 2026, 07:03 AM UTC· resolved Apr 02, 2026, 02:13 PM UTC

1. investigating Mar 31, 2026, 07:03 AM UTC

   We are investigating an issue with purge and edge delivery related to intermittent failures, latency and/or 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/.

2. investigating Mar 31, 2026, 07:17 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/0D5a7000011IxVDCA0. We will provide the next update as we make progress.

3. investigating Mar 31, 2026, 11:10 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/0D5a7000011IxVDCA0.

4. investigating Mar 31, 2026, 04:18 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/0D5a7000011IxVDCA0.

5. investigating Mar 31, 2026, 09:56 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/0D5a7000011IxVDCA0.

6. resolved Apr 02, 2026, 02:13 PM UTC

   We can confirm that the issue was mitigated at 14:00 UTC on April 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/0D5a7000011IxVDCA0 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 Mar 19, 2026, 04:38 PM UTC· resolved Mar 23, 2026, 05:59 PM UTC

1. investigating Mar 19, 2026, 04:38 PM UTC

   We are investigating an emerging issue with our Enhanced TLS Delivery Network related to intermittent TLS errors against Akamaized hostnames for customers who are using OpenJDK. 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 Mar 19, 2026, 05:02 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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes.

3. investigating Mar 19, 2026, 06: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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes.

4. investigating Mar 19, 2026, 07:05 PM UTC

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

5. investigating Mar 19, 2026, 08:05 PM UTC

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

6. investigating Mar 19, 2026, 09:03 PM UTC

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

7. investigating Mar 19, 2026, 09: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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes.

8. investigating Mar 19, 2026, 11:00 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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes

9. investigating Mar 19, 2026, 11:55 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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes

10. investigating Mar 20, 2026, 12:55 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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes

11. resolved Mar 23, 2026, 05:59 PM UTC

    We can confirm that the issue was mitigated at 18:35 UTC on March 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/0D5a700000zYYneCAG 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 Mar 17, 2026, 09:57 AM UTC· resolved Mar 17, 2026, 12:19 PM UTC

1. investigating Mar 17, 2026, 09:57 AM UTC

   We are investigating an emerging issue with Enterprise Application Access (EAA) related to device postures. We are actively investigating the issue and will provide another update within the next 120 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 Mar 17, 2026, 11:39 AM UTC

   We've engaged the necessary subject matter experts and are continuing to investigate this issue. We will continue to post updates as more information is available.

3. resolved Mar 17, 2026, 12:19 PM UTC

   We can confirm that the issue was mitigated at 12:00 UTC on March 17, 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/0D5a700000z74q9CAA 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 Mar 13, 2026, 06:39 PM UTC· resolved Mar 13, 2026, 07:57 PM UTC

1. investigating Mar 13, 2026, 06:39 PM UTC

   We are investigating an emerging issue with Account Protector, Bot Manager Premier, Enterprise Application Access (EAA), and ETP/SIA (Secure Internet Access) related to connectivity issues at the Compute Washington Data Center beginning at approximately 18:00 UTC. 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/0D5a700000yhjlyCAA. 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 Mar 13, 2026, 07:01 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/0D5a700000yhjlyCAA. We will provide an update within the next 60 minutes.

3. resolved Mar 13, 2026, 07:57 PM UTC

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

4. postmortem Mar 17, 2026, 08:47 PM UTC

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

Read the full incident report →

Started Mar 10, 2026, 05:49 PM UTC· resolved Mar 10, 2026, 05:49 PM UTC

1. resolved Mar 10, 2026, 05:49 PM UTC

   We became aware of an issue with Edge Delivery related to performance degradation in Dallas, US. The issue lasted between 14:37 UTC and 15:43 UTC on March 10, 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/0D5a700000y8scWCAQ 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 Mar 10, 2026, 05:38 PM UTC· resolved Mar 10, 2026, 10:00 PM UTC

1. investigating Mar 10, 2026, 05:38 PM UTC

   We are investigating an emerging issue with multiple Akamai products related to DNS malicious filtering where users may encounter fully qualified domain names (FQDNs) erroneously being flagged as malicious. 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 Mar 10, 2026, 06:04 PM UTC

   We are continuing to investigate this issue. We identified that the components listed on this status page were incorrectly marked when the update was created. We have now corrected this to reflect the accurately impacted components. We apologize for any confusion this may have caused. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

3. identified Mar 10, 2026, 06: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/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

4. identified Mar 10, 2026, 08:08 PM UTC

   We continue to work on implementing a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

5. monitoring Mar 10, 2026, 09:03 PM UTC

   We continue to work on implementing a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.

6. resolved Mar 10, 2026, 10:00 PM UTC

   We can confirm that the issue was mitigated at 20:39 UTC on March 10, 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 Mar 09, 2026, 07:28 PM UTC· resolved Mar 09, 2026, 10:36 PM UTC

1. investigating Mar 09, 2026, 07:28 PM UTC

   We are investigating an emerging issue with Account Protector, Bot Manager Premier, Enterprise Application Access (EAA), and ETP/SIA related to Compute connectivity issues beginning at approximately 18:10 UTC. 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 Mar 09, 2026, 07:53 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/0D5a700000y0QksCAE. We will provide an update within the next 60 minutes.

3. investigating Mar 09, 2026, 08:55 PM UTC

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

4. monitoring Mar 09, 2026, 09:32 PM UTC

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

5. resolved Mar 09, 2026, 10:36 PM UTC

   We can confirm that the issue was mitigated at 21:16 UTC on March 9, 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 Mar 07, 2026, 07:00 PM UTC· resolved Mar 07, 2026, 10:06 PM UTC

1. investigating Mar 07, 2026, 07:00 PM UTC

   We are investigating an emerging issue with Bot Manager Premier related to legitimate traffic being blocked with elevated false positives. 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 Mar 07, 2026, 07:55 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/0D5a700000xlBv4CAE. We will provide an update within the next 60 minutes.

3. identified Mar 07, 2026, 08:49 PM UTC

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

4. identified Mar 07, 2026, 09:43 PM UTC

   We are continuing to implement a fix for this issue. Thank you for your patience. We will provide an update within the next 60 minutes.

5. resolved Mar 07, 2026, 10:06 PM UTC

   We can confirm that the issue was mitigated at 22:00 UTC on March 7, 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/0D5a700000xlBv4CAE, 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 Feb 27, 2026, 09:32 PM UTC· resolved Mar 03, 2026, 05:32 PM UTC

1. monitoring Feb 27, 2026, 09:32 PM UTC

   We became aware of a reoccurrence of the issue with a third-party service provider causing degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region related to https://www.akamaistatus.com/incidents/m5z1b82n5h0z. The issue lasted between 19:45 UTC and 21:00 UTC on February 27, 2026. We have taken mitigation steps and escalated to our third-party service provider to investigate the additional period of impact; 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/0D5a700000wQl7YCAS. 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.

2. investigating Feb 28, 2026, 11:16 AM UTC

   We are aware of an ongoing reoccurrence of this issue starting from 09:17 UTC on February 28, 2026, which may cause degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region. We are continuing to work with our third-party service provider to nvestigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will provide an update within the next 120 minutes.

3. investigating Feb 28, 2026, 12:26 PM UTC

   We have been able to apply mitigation actions that improve the experience for customers connecting to the Mumbai, IN region, and continue working 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/0D5a700000wQl7YCAS. We will provide an update as we make progress.

4. monitoring Feb 28, 2026, 05:43 PM UTC

   We have taken mitigation steps and escalated to our third-party service provider who confirmed the impact was caused due to ongoing restoration activities on their cable system during that period, which has been completed.; based on current observations as of 13:40 UTC on February 28, 2026, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will continue to monitor to ensure that the impact has been fully mitigated.

5. resolved Mar 03, 2026, 05:32 PM UTC

   We can confirm that the issue was mitigated at 13:40 UTC on February 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/0D5a700000wQl7YCAS, 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 Feb 19, 2026, 08:22 PM UTC· resolved Feb 19, 2026, 09:50 PM UTC

1. investigating Feb 19, 2026, 08:22 PM UTC

   We are investigating an emerging issue with Content Purge related to 503 error responses to a portion of purge requests submitted via API. 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 Feb 19, 2026, 09:50 PM UTC

   We can confirm that the issue was mitigated at ~19:00 UTC on February 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/0D5a700000uxhxXCAQ?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 Feb 11, 2026, 09:09 PM UTC· resolved Mar 20, 2026, 07:17 PM UTC

1. identified Feb 11, 2026, 09:09 PM UTC

   We are investigating an emerging issue with Certificate Provisioning System (CPS) where users may have issue accessing via Akamai control center. The issue is identified and we are actively working the mitigation plan and will provide another update as progress is made.

2. monitoring Feb 11, 2026, 11:05 PM UTC

   We have implemented a fix for this issue as of 22:10 UTC on 11 February 2026; based on current observations, the service is resuming normal operations. We will continue to monitor until tomorrow US afternoon hours to ensure that the impact has been fully mitigated.

3. monitoring Feb 12, 2026, 08:04 PM UTC

   We have implemented a fix for this issue as of 22:10 UTC on 11 February 2026; based on current observations, the service is resuming normal operations. We will continue to monitor for one additional day until tomorrow US afternoon hours to ensure that the impact has been fully mitigated.

4. monitoring Feb 13, 2026, 09:19 PM UTC

   After implementing the fix and based on current observations, the service continues to operate within normal parameters. We will continue monitoring throughout the weekend to ensure the issue has been fully mitigated. The next update will be provided on Monday, February 16, 2026, during U.S. afternoon hours. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000tGYakCAG.

5. monitoring Feb 17, 2026, 12:32 AM UTC

   We continue our monitoring and the service continues to operate within normal parameters. We will continue monitoring until tomorrow Tuesday February 17th to ensure the issue has been fully mitigated. The next update will be provided during U.S. afternoon hours.

6. monitoring Feb 18, 2026, 12:27 AM UTC

   We are investigating a recurrence of this issue with Certificate Provisioning System (CPS) where users may have issues accessing via Akamai control center. The recurrence started at approximately 23:20 UTC on February 17th, 2026. The issue is confirmed to be no longer causing impact as of 23:45 UTC on February 17th, 2026. We have decided to continue our monitoring overnight and will provide another update as progress is made.

7. monitoring Feb 19, 2026, 12:24 AM UTC

   We continue our monitoring and the service continues to operate within normal parameters. We will continue monitoring until mid next week to ensure the issue has been fully mitigated. The next update will be provided next week during U.S. afternoon hours.

8. monitoring Feb 27, 2026, 12:36 AM UTC

   We continue our monitoring and the service continues to operate within normal parameters. We will continue monitoring until mid next week to ensure the issue has been fully mitigated. The next update will be provided next week on Wednesday March 4th during U.S. afternoon hours at the latest.

9. monitoring Mar 04, 2026, 09:22 PM UTC

   We identified that this issue was caused by a software defect that impacted our automated database maintenance procedures. As an immediate mitigation, our team performed manual database maintenance to stabilize the system and restore normal operations, we can confirm the service continues to operate within normal parameters. Also as a long term mitigation, we are also releasing additional software changes to correct the underlying issue and prevent this condition from recurring. We will continue monitoring closely as the updates roll out and will provide further updates as appropriate. Next scheduled update should arrive after March 18th.

10. monitoring Mar 19, 2026, 10:38 PM UTC

    As of 17:00 UTC on March 19th, 2026; we have completed the software change to correct and prevent the condition that caused this issue from recurring. In abundance of caution, we will monitor closely until tomorrow March 20th, 2026 at 18:00 UTC. Next scheduled update should arrive March 20th, 2026 after 18:00 UTC.

11. resolved Mar 20, 2026, 07:17 PM UTC

    We can confirm that the issue was mitigated at 17:00 UTC on March 19th, 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/0D5a700000tGYakCAG 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 Feb 10, 2026, 10:24 PM UTC· resolved Feb 11, 2026, 12:13 AM UTC

1. investigating Feb 10, 2026, 10:24 PM UTC

   We are investigating an emerging issue with the Akamai Control Center. Affected users may receive errors when attempting to access applications in the Control Center. 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 Feb 10, 2026, 11:09 PM UTC

   We've engaged the necessary subject matter experts and are continuing to investigate this issue. We will continue to post updates as more information is available.

3. identified Feb 10, 2026, 11:48 PM UTC

   We have identified the cause of the issue, and a fix is being implemented. Customers have been contacted with instructions to mitigate impacts to their systems or services. We will provide an update within the next 60 minutes.

4. resolved Feb 11, 2026, 12:13 AM UTC

   We can confirm that the issue was mitigated at 23:58 UTC on February 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/0D5a700000tQzoNCAS 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 Feb 10, 2026, 12:23 AM UTC· resolved Feb 10, 2026, 05:41 PM UTC

1. investigating Feb 10, 2026, 12:23 AM UTC

   We are investigating an emerging issue with Certificate Provisioning System (CPS) where users may have issue accessing via Akamai control center. 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 Feb 10, 2026, 12:47 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/0D5a700000tGYakCAG. We will provide an update within the next 60 minutes.

3. investigating Feb 10, 2026, 01:46 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/0D5a700000tGYakCAG. We will provide the next update as we make progress.

4. monitoring Feb 10, 2026, 04:27 AM UTC

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

5. resolved Feb 10, 2026, 05:41 PM UTC

   We can confirm that the issue was mitigated at 03:22 UTC on 10 February 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/0D5a700000tGYakCAG 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 Jan 30, 2026, 02:14 PM UTC· resolved Feb 04, 2026, 01:33 AM UTC

1. investigating Jan 30, 2026, 02:14 PM UTC

   We are investigating an emerging issue with Enterprise Center related to the Enterprise Center user interface in Akamai Control Center where customers may encounter intermittent slowness and occasional failures. 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 Jan 30, 2026, 03:04 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/0D5a700000rj0IvCAI. We will provide an update within the next 60 minutes.

3. investigating Jan 30, 2026, 04:10 PM UTC

   We are continuing to investigate this issue.

4. investigating Jan 30, 2026, 06:39 PM UTC

   We are continuing to investigate this issue. Subsequent updates around mitigation status will be posted as progress is made.

5. monitoring Jan 30, 2026, 08:59 PM UTC

   We have not experienced a reoccurrence of this issue since approximately 12:10 UTC on January 30, 2026; 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/0D5a700000rj0IvCAI. We will continue to monitor to ensure that the impact has been fully mitigated.

6. monitoring Feb 03, 2026, 06:35 PM UTC

   We are continuing to monitor this issue. Based on current observations, the service is operating normally. We will provide updates if the situation changes.

7. resolved Feb 04, 2026, 01:33 AM UTC

   We can confirm that the issue was mitigated at 00:07 UTC on February 4, 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/0D5a700000rj0IvCAI 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 Jan 26, 2026, 01:00 PM UTC· resolved Jan 26, 2026, 01:00 PM UTC

1. resolved Jan 26, 2026, 06:07 PM UTC

   We recently became aware of an issue with the Certificate Provisioning System (CPS) user interface in Akamai Control Center (ACC) where users experienced "Akamai Control Center has experienced an error, please try again. If the problem persists, contact Akamai Technical Support." errors. The issue also affected the Certificate Provisioning System (CPS) API requests. The impact occurred between approximately 13:00 and 15:30 UTC on 26 January 2026. We can confirm that the issue is 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/0D5a700000qx5z6CAA, 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 Jan 23, 2026, 07:14 PM UTC· resolved Jan 27, 2026, 06:56 PM UTC

1. monitoring Jan 23, 2026, 07:14 PM UTC

   Akamai is aware of an upcoming winter storm set to affect the continental United States during the upcoming days (https://www.wpc.ncep.noaa.gov/wwd/wssi/wssi.php). Akamai is working with our vendors to ensure proper preparedness to withstand the storm and take actions in case they are needed. We are actively monitoring the situation to ensure that services remain stable. 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 Jan 27, 2026, 06:56 PM UTC

   After monitoring our systems, we haven’t observed any issues with our services related to the winter storm. We will now consider this notification resolved.

Read the full incident report →

Started Jan 13, 2026, 08:52 AM UTC· resolved Jan 13, 2026, 08:52 AM UTC

1. resolved Jan 13, 2026, 08:52 AM UTC

   We became aware of an issue with Edge Delivery Network related to connectivity time outs and latency issues with packet loss alerts. The issue lasted between 7:00 UTC and 7:30 UTC on 13th January, 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/0D5a700000p67z7CAA 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 Jan 08, 2026, 12:54 PM UTC· resolved Jan 09, 2026, 07:05 PM UTC

1. investigating Jan 08, 2026, 12:54 PM UTC

   We are investigating an emerging issue with a third-party service provider causing failure with Domain Name Service (DNS) configured with Secure Internet Access (SIA) in India region. 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 Jan 08, 2026, 01:38 PM UTC

   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/0D5a700000oZGLXCA4We will provide an update within the next 90 minutes.

3. investigating Jan 08, 2026, 03:01 PM UTC

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

4. investigating Jan 08, 2026, 04:01 PM UTC

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

5. monitoring Jan 08, 2026, 11:09 PM UTC

   We have implemented a fix to mitigate this issue as of ~16:45 UTC on January 8, 2026; based on current observations, the service is resuming normal operations. We continue to work with our third-party service provider to fully resolve the issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000oZGLXCA4. We will continue to monitor to ensure that the impact has been fully mitigated.

6. resolved Jan 09, 2026, 07:05 PM UTC

   We can confirm that the issue was mitigated at 11:47 UTC on January 9, 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/0D5a700000oZGLXCA4 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 Dec 22, 2025, 08:40 AM UTC· resolved Dec 24, 2025, 04:59 AM UTC

1. investigating Dec 22, 2025, 08:40 AM UTC

   We are investigating an emerging issue with TLS Provisioning related to Certificate Provisioning System API calls returning 429 - "Too Many Requests" response codes. We are actively investigating the issue and will provide another update within the next 120 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 Dec 22, 2025, 09: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/0D5a700000mklwcCAA.

3. investigating Dec 22, 2025, 11: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/0D5a700000mklwcCAA. We will provide an update within the next 120 minutes.

4. investigating Dec 22, 2025, 01: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/0D5a700000mklwcCAA. We will provide an update within the next 120 minutes.

5. investigating Dec 22, 2025, 02:40 PM UTC

   We are making some backend adjustments to mitigate the impact. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000mklwcCAA. We will provide an update within the next 120 minutes.

6. investigating Dec 22, 2025, 04:38 PM UTC

   We are continuing to do some additional backend adjustments to mitigate the impact. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000mklwcCAA. We will provide an update within the next 120 minutes.

7. investigating Dec 22, 2025, 06:52 PM UTC

   We are continuing to do some additional backend adjustments to mitigate the impact. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000mklwcCAA. Subsequent updates around mitigation status will be posted as progress is made.

8. monitoring Dec 22, 2025, 08:11 PM UTC

   We have implemented a fix for this issue as of 16:55 UTC on December 22, 2025; 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/0D5a700000mklwcCAA. We will continue to monitor to ensure that the impact has been fully mitigated.

9. resolved Dec 24, 2025, 04:59 AM UTC

   We can confirm that the issue was mitigated at 16:55 UTC on December 22, 2025, 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/0D5a700000mklwcCAA 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.

10. postmortem Dec 30, 2025, 02:19 PM UTC

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

Read the full incident report →

Started Dec 15, 2025, 07:14 PM UTC· resolved Dec 19, 2025, 02:28 PM UTC

1. monitoring Dec 15, 2025, 07:14 PM UTC

   We became aware of an issue with Edge Delivery related to potential latency and timeouts in traffic sent between Singapore and Chennai. The issue lasted between 16:20 UTC and 18:41 UTC on December 15, 2025. We have implemented a fix while we continue working with our third-party service provider; 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/0D5a700000lx29lCAA. 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.

2. resolved Dec 19, 2025, 02:28 PM UTC

   We can confirm that the issue was mitigated at 18:00 UTC on December 15, 2025, 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/0D5a700000lx29lCAA 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.18:00

Read the full incident report →