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.
State
Investigating
Started
10 d ago
2026-10-23 12:00 UTC
Ongoing for
10 days
Worst impact
Notice
Timeline
1 updateInvestigating
10 days 100%
Updates
Times in UTCAs posted by Akamai
Our investigation has revealed that a significant majority of our Platform is not affected by this CVE. We are continuing to investigate this issue to evaluate possible impact to customers and remaining Akamai products. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAI. We will provide an update as we progress.
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
10× the median
Other Akamai incidents
All incidentsAkamai·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.
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.
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
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.
Akamai·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.
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=akamaiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane