Akamai did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-22 20:17 UTC. This page shows the end time when Akamai marks it resolved.

How do I get alerts for Akamai?

Subscribe to the Akamai live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Akamai. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

AkamaiIncident · 2026-10-22 20:17 UTC

Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities

Q: What happened?

Akamai reported "Customer Security Advisory: Critical F5/NGINX Out-of-Band Vulnerabilities" on its status page at 2026-10-22 20:17 UTC. Akamai reports a possible impact from the F5/NGINX vulnerabilities CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479 on its platform and infrastructure. Akamai continues to investigate and monitors the situation. Customers with a valid Control Center login can find more details in the Akamai Community.

NoticeOfficial update

Akamai reports a possible impact from the F5/NGINX vulnerabilities CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479 on its platform and infrastructure. Akamai continues to investigate and monitors the situation. Customers with a valid Control Center login can find more details in the Akamai Community.

State

Monitoring

Started

10 d ago

2026-10-22 20:17 UTC

Ongoing for

10 days

Worst impact

Notice

Timeline

1 update

Oct 22Oct 25Oct 27Oct 30Nov 1

NoticeUpdate postedDates in UTC

Monitoring

10 days 100%

Updates

Times in UTC

As posted by Akamai

Monitoring2026-11-01 17:18 UTC

Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing impact related to this issue, please use the Support Center on Akamai Community or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

Akamai in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

22 h 16 min

This incident

11× the median

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

20 days

median 22 h 16 min

90 days agoToday

Other Akamai incidents

All incidents

Akamai·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.

Noticeupdated 2 d ago

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.

Noticeupdated 5 d ago

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.

Resolvedresolved 5 d ago

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.

Degradedupdated 4 d ago

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.

Noticeupdated 4 d ago

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

RSS

https://outages.cc/feed.xml?providers=akamai

Slack

/feed subscribe https://outages.cc/feed.xml?providers=akamai

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane