Akamai experienced a minor incident on December 22, 2025 affecting TLS Provisioning (Certificates, CPS), lasting 1d 20h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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/.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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