Akamai Status

Monitoring: [Our third-party service provider has | We have] [implemented a fix for | rolled back a release which we believe may have caused] this issue as of [time in UTC] on [DD Month, YYYY]; based on current observations, the service is resuming normal operations. [Customers and partners can find more details on the Akamai Community: <link>.] We will continue to monitor to ensure that the impact has been fully mitigated.

Investigating: We are continuing to [work with our third-party service provider to] investigate this issue. [Customers and partners can find more details on the Akamai Community: <link>.] [We will provide an update within the next XX minutes.]

Investigating: We are continuing to [work with our third-party service provider to] investigate this issue. [Customers and partners can find more details on the Akamai Community: <link>.] [We will provide an update within the next XX minutes.]

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

Monitoring: We have implemented a fix for this issue as of 02:50 UTC on 8 May 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/0D5a700000P9EP2CAN. We will continue to monitor to ensure that the impact has been fully mitigated.

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

Investigating: We are investigating an issue with configuration deployment related to activation delays. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

Resolved: We can confirm that the issue was mitigated at 17:34 UTC on May 7, 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/0D5a700000P17C1CAJ, 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.

Identified: 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. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000P17C1CAJ. We will provide the next update as we make progress.

Investigating: We are actively investigating this issue. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000P17C1CAJ. We will provide additional updates as further progress is made.

Investigating: We are investigating an emerging issue with Certificate Provisioning System (CPS) where the user interface fails to display the correct SAN list for a certificate when a user chooses to exclude SAN name(s) on the certificate from the DNS name list on the associated slot. We are actively working with the appropriate SMEs and will provide another update as progress is made. 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/.