Akamai: Increased latency during upstream provider maintenance in Singapore, Hong Kong, and Japan
Affected components: Content Delivery - Edge DeliveryEdge Delivery
Timeline of updates
- investigating
Scheduled upstream provider maintenance is currently taking place along network routes connecting Singapore, Hong Kong, and Japan from September 18, 2026 at 06:30 UTC through October 3, 2026 at 23:59 UTC. While core service remains operational, customers in the affected regions may notice increased latency during peak traffic hours. We are monitoring network performance until maintenance concludes.Customers and partners with a valid Control Center login can find updates 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/.
- investigating
We will continue to monitor the network performance until the maintenance concludes. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V0be8CAB. We will provide the next update as we make progress.
- resolved
We can confirm that the issue was mitigated on September 30, 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/0D5a700001V0be8CAB 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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).