Live

Customer Security Advisory: CVE-2026-114938

Major outageOfficial update
0

Akamai reports a major outage that affects the Customer Security Advisory and the Customer Service, Documentation and Community Customer Security Advisory components. Akamai is investigating the issue. Akamai is assessing the Java4Shell vulnerability CVE-2026-114938 and says its security teams are taking mitigation measures.

State

Investigating

Started

Ongoing for

3 h 44 min

Worst impact

Major outage

Timeline

1 update
09:3110:2711:2312:1913:15
Major outageUpdate postedTimes in UTC

Investigating

3 h 44 min 100%

Updates

Times in UTC

As posted by Akamai

Investigating

Akamai is aware of the recently identified Java4Shell Remote Code Execution (RCE) vulnerability, tracked as CVE-2026-114938.We are actively assessing the potential impact of this vulnerability across our platform and services. Our security teams are engaged and are taking appropriate mitigation measures to address any potential exposure.Akamai is prioritizing this effort and will continue to monitor the situation closely. We will provide further updates as additional information becomes available.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/.

Affected components

2
Customer Security AdvisoryCustomer Service, Documentation and Community - Customer Security Advisory

Akamai in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

34

Days with an incident

63

Median duration

22 h 14 min

This incident

83% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 days
median 22 h 14 min
90 days agoToday

Other Akamai incidents

All incidents

Akamai·Configuration Deployment delays

Akamai reports delays in fast changes on multiple Fast Metadata Activation channels and in moving security configuration to production. Akamai is investigating the issue.

Degraded

Akamai·Edge Delivery Issues in Singapore and Japan Regions

Akamai reports performance degradation on Edge Delivery and Content Delivery Edge Delivery in the Singapore and Japan regions. Akamai implemented a fix and Edge Delivery resumed healthy service at about 18:15 UTC on November 17, 2026. The status is monitoring.

Degraded

Akamai·Application Load Balancer reporting availability issues

Akamai reports that Application Load Balancer reporting and Data Services - Reporting had availability errors. Akamai identified the cause and applied a fix. Akamai resolved the incident at 14:36 UTC on November 16, 2026, after about 10 hours and 48 minutes.

Resolved

Akamai·Customer Security Advisory: Remote code execution vulnerability in the Apache HTTP Server's HTTP/2 module

Akamai reports a security advisory for a remote code execution vulnerability in the Apache HTTP Server HTTP/2 module. This affects the Customer Security Advisory component and the Customer Service, Documentation and Community advisory. Akamai is investigating the potential impact across its platform and infrastructure, and reports no evidence that the vulnerability has been exploited on any Akamai platform or product.

Major outage

Akamai·Email Systems Widespread Outage

Akamai reports that its email systems and the email part of Customer Service, Documentation and Community did not work correctly. Akamai resolved the issue on November 13, 2026, and reports that normal operation resumed. The outage lasted about 22 hours.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=akamai
Slack
/feed subscribe https://outages.live/feed.xml?providers=akamai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane