← Back to Akamai History
minormonitoring
Certificate Provisioning System (CPS) recurrence of issues in Akamai Control Center Portal
Status
monitoring
Duration
Ongoing
Updates
9
Coverage
0 articles
INCIDENT TIMELINE
monitoringWed, Mar 4, 2026, 09:22 PM
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.
monitoringFri, Feb 27, 2026, 12:36 AM
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.
monitoringThu, Feb 19, 2026, 12:24 AM
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.
monitoringWed, Feb 18, 2026, 12:27 AM
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.
monitoringTue, Feb 17, 2026, 12:32 AM
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.
monitoringFri, Feb 13, 2026, 09:19 PM
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.
monitoringThu, Feb 12, 2026, 08:04 PM
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.
monitoringWed, Feb 11, 2026, 11:05 PM
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.
identifiedWed, Feb 11, 2026, 09:09 PM
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.
📊 TECHNICAL DETAILS
Internal ID
9c82a8aa-4b47-4e13-88fa-e8d22566af71
External ID
23fbn79n9b8h
🕐 Started
Wed, Feb 11, 2026, 09:09 PM
🔄 Last Updated
Wed, Mar 4, 2026, 09:22 PM
MINOR
Impact Level
Ongoing
Total Duration
9
Status Updates
Affected Components
TLS Provisioning
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed