Live

Edge Delivery Issues in Singapore and Japan Regions

0

Akamai reports degraded Edge Delivery and Content Delivery in the Singapore and Japan regions. Akamai is investigating the issue and continues to investigate it. Akamai gives no cause and no workaround.

State

Investigating

Started

Ongoing for

1 h 4 min

Worst impact

Degraded

Timeline

2 updates
17:4017:5618:1318:2918:45
DegradedUpdate postedTimes in UTC

Investigating

1 h 4 min 100%

Updates

Times in UTC

As posted by Akamai

Investigating

We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001fiQ7QCAU. We will provide an update within the next 60 minutes.

Investigating

We are investigating an emerging issue with Cloud Wrapper related to Edge Delivery where customers may experience performance degradation issues like latency, video playback failures, packet drops etc in the Singapore region. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. 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
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

63

Median duration

22 h 14 min

This incident

95% 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·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

Akamai·Property Manager Property Activation Errors

We became aware of an issue with Property Manager related to activating properties with errors indicating "cloudlet policy not found or not valid" blocking some property activations. The issue lasted between approximately 15:30 UTC on November 3, 2026 and 17:15 UTC on November 3, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.

Resolved

Akamai·Customer Security Advisory: CVE-2026-98432

The Akamai Customer Community is not available. This affects the Akamai Customer Community component and customer service, documentation, and community services. Akamai reports that the issue is resolved. The outage lasted from 30 October 2026 to 9 November 2026, about 10 days.

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