Certificate Provisioning System (CPS) issues
We can confirm that the issue was mitigated at 03:34 UTC on 19 August, 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/0D5a700001PHy9qCAD 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.
The latest update from Akamai.
State
Resolved
Started
74 d ago
2026-08-19 16:10 UTC
Lasted
22 h 36 min
until 2026-08-20 14:46 UTC
Worst impact
Notice
Timeline
3 updatesMonitoring
22 h 36 min 100%
Updates
Times in UTCAs posted by Akamai
We can confirm that the issue was mitigated at 03:34 UTC on 19 August, 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/0D5a700001PHy9qCAD 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.
We are continuing to monitor for any further issues.
We became aware of an issue with the Certificate Provisioning System (CPS) involving timeouts in the User Interface of Akamai Control Center, as well as errors when using the API. The issue lasted between 03:12 UTC on 19 August 2026 and 03:34 UTC on 19 August 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/0D5a700001PHy9qCAD. 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.
Affected components
2Akamai in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
58
Median duration
22 h 16 min
This incident
About the median
Other Akamai incidents
All incidentsAkamai·Customer Security Advisory: CVE-2026-98432
Akamai reports an operational issue with the Akamai Customer Community and related Customer Service and Documentation components. Akamai is investigating. More details are on the Akamai Community page.
Akamai·Performance Degradation for Customers in Mumbai and Chennai
Akamai reports performance degradation for customers in Mumbai and Chennai. The affected components are Edge Delivery and Content Delivery - Edge Delivery. Akamai is investigating, and the packet loss has subsided.
Akamai·Enterprise Application Access (EAA) Connector Issues
We can confirm that the issue was mitigated at 08:30 UTC on 27 October 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/0D5a700001bU4YFCA0 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.
Akamai·Edge Delivery issues between Indonesia and Singapore
Edge Delivery does not work correctly between Indonesia and Singapore. Content Delivery - Edge Delivery is affected. Akamai reports that the state is monitoring.
Akamai·Customer Security Advisory: Brotli Remote Code Execution Vulnerabilities
Akamai reports that Brotli remote code execution vulnerabilities affect the Akamai Customer Community components. Akamai states that most of its platform is not affected by this CVE. Akamai is investigating the issue and will give an update.
Follow Akamai
Your coding agent knows when Akamai is down, and tells you when a failure is theirs, not yours. You can also get Akamai incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "akamai" and tell me if Akamai has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=akamai/feed subscribe https://outages.cc/feed.xml?providers=akamaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane