Live

Origin Server Connectivity Issues with Elevated Errors in APAC Region

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.

The latest update from Akamai.

State

Resolved

Started

40 d ago

2026-09-22 14:28 UTC

Lasted

20 days

until 2026-10-12 23:08 UTC

Worst impact

Degraded

Timeline

5 updates
Sep 22Sep 27Oct 2Oct 7Oct 12
DegradedUpdate postedDates in UTC

Monitoring

20 days 100%

Updates

Times in UTC

As posted by Akamai

Resolved2026-10-12 23:08 UTC

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.

Monitoring2026-09-28 10:01 UTC

Our upstream carrier continues to work on the maintenance of the impacted subsea cables. Although immediate impact has subsided, customers may still experience intermittent impact until the repair works are completed - the current estimate points to early October, 2026, subject to change. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN. We will continue to monitor to ensure that the impact has been fully mitigated.

Monitoring2026-09-22 21:06 UTC

We are continuing to monitor to ensure the impact has been fully mitigated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN

Monitoring2026-09-22 14:28 UTC

We have identified that this issue was likely due to upstream congestion related to unexpected maintenance on subsea cables. The impact was primarily observed when requests from outside the APAC region were routed to origins in the APAC region, and when requests from the APAC region were routed to origins outside the region. We are working with the upstream ISP(s) to gather additional details.Based on our current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN. We will continue to monitor to ensure the impact has been fully mitigated.

Monitoring2026-09-22 13:19 UTC

We became aware of an issue with origin server connectivity that caused intermittent connectivity issues and elevated errors for some customers in affected regions. The issue was resolved at approximately 11:41 UTC on 22 September, 2026. The issue appears to have self-corrected; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure 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 help prevent a recurrence of this issue.

Affected components

2
Edge DeliveryContent Delivery - Edge Delivery

Akamai in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

32

Days with an incident

58

Median duration

22 h 16 min

This incident

22× 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