Akamai
Akamai is operational
Edge Delivery issues between Indonesia and Singapore
Akamai Edge Delivery and Content Delivery - Edge Delivery have issues between Indonesia and Singapore. The service is degraded. Akamai reports that the impact is under monitoring and continues to monitor the impact.
Customer Security Advisory: CVE-2026-98432
The Akamai Customer Community does not work. This issue affects the Akamai Customer Community component under Customer Service, Documentation and Community. Akamai is investigating the issue. More details are on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a700001cIGoWCAW.
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.
Customer Security Advisory: Brotli Remote Code Execution Vulnerabilities
Akamai reports an issue that affects the Akamai Customer Community components. Akamai is investigating the issue. Akamai reports that most of its platform is not affected. More details are in the Akamai Community post.
Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities
Akamai investigates the possible impact of the F5/NGINX vulnerabilities CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479 on its platform and infrastructure. Akamai reports the status as monitoring. Customers with a Control Center login can find details in the Akamai Community incident notification group.
History
Incidents in 90 days
32
Days with an incident
58
Median duration
22 h 16 min
Longest incident
20 days
Components
42Customer Service, Documentation and Community
Content Delivery
Data Services
Configuration
Enterprise Security
Oct 21, 2026
Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0www.akamaistatus.com
Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAKwww.akamaistatus.com
Customers and partners can find an incident summary report, here: [https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC](https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC)www.akamaistatus.com
We can confirm that the issue was mitigated at approximately 22:00 UTC on 21 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/0D5a700001aOfDBCA0 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.www.akamaistatus.com
Sep 22, 2026
We can confirm that the issue was mitigated at 11:41 UTC on 22 September 2026, and the service has resumed normal operation. We have not observed any related impact to the Akamai platform since the issue self-corrected.We remain in contact with our upstream providers and continue to monitor the related repair work for this incident. Customers and partners can view additional details by logging in to the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN or by contacting Akamai Support.We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to help prevent recurrence.www.akamaistatus.com
We can confirm that the issue was mitigated on September 30, 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/0D5a700001V0be8CAB 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.www.akamaistatus.com
Sep 4, 2026
We became aware of an issue with a network component related to connectivity in the Atlanta, GA region which impacted the Certificate Provisioning System as well as potential impact to other Edge traffic through the region. The issue lasted between 12:21 UTC and 14:19 UTC on September 4, 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: 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.www.akamaistatus.com
We can confirm that the issue was mitigated at 14:20 UTC on 4 September, 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/0D5a700001S7tYbCAJ 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.www.akamaistatus.com
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.live/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.live/feed.xml?providers=akamai/feed subscribe https://outages.live/feed.xml?providers=akamaiGo from tracking outages to fixing production issues with Polylane.
Try Polylane