Origin Server Connectivity Issues with Elevated Errors in APAC Region

What to do

• Check whether you use Akamai Edge Delivery in apac. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 20d 8h it lasted.

  Anything that failed between 2026-09-22 14:28 UTC and 2026-10-12 23:08 UTC may need a replay.

• Subscribe to Akamai's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=akamai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai 5

1. monitoringSep 22, 2026, 1:19 PM 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.

   provider

2. monitoringSep 22, 2026, 2:28 PM 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.

   provider

3. monitoringSep 22, 2026, 9:06 PM 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

   provider

4. monitoringSep 28, 2026, 10:01 AM 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.

   provider

5. resolvedOct 12, 2026, 11:08 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.