Akamai's Edge Delivery service ran into performance degradation and timeouts between Indonesia and Singapore starting at 13:44 UTC on 25 October 2026. The fault sat on Akamai's side of the network, and as of the last update it was still being monitored for full recovery.
Started
13:44 UTC
Duration
Lasted 22d 4h
Source
IsDown
Next time
Akamai is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Edge Delivery
What happened?
Akamai opened this incident at 13:44 UTC, reporting an emerging issue with Edge Delivery causing performance degradation and timeouts specifically between Indonesia and Singapore. The one component affected on Akamai's status page is Edge Delivery, and no other components were listed as impacted. An hour later, at 14:43 UTC, Akamai said it was working with a third-party service provider to investigate, without naming that provider or explaining what role it played in the fault. At 16:06 UTC Akamai posted that a fix had been implemented, and pointed to 13:11 UTC on 25 October as the effective time of that fix, which is before the incident was even opened on the public page. Akamai described the service as resuming normal operations at that point, but kept the incident in a monitoring state rather than closing it. A further update, timestamped 09:13, repeated that monitoring would continue to confirm the impact had been fully mitigated, with no new details added. That is four updates in total, and all four are shown here. No root cause has been published for why the Indonesia to Singapore path degraded, and Akamai has not said whether the third-party provider's problem was the underlying trigger. No user reports were filed during this window, so there is no independent confirmation of impact from people experiencing it directly. As it stands, the incident is still open, with the last word from Akamai being that monitoring is ongoing.
Learning
UptimeRobot's own probes for Akamai's edge reachability, run from EU and North America, show 100% uptime over the last 24 hours, 7 days and 30 days, and this incident was not registered as a hit against those checks. That is not a contradiction. The fault described by Akamai was a regional path issue affecting delivery between Indonesia and Singapore, and probes based in Europe and North America simply were not positioned to see a performance problem confined to that specific route. This is a useful shape to recognise: a provider's edge network can degrade badly for a defined geography while synthetic checks run from other regions stay green the whole time, because they are testing a different path through the network. If your product serves traffic through that Indonesia to Singapore corridor, your own uptime dashboard could easily have looked fine while actual requests were timing out. Akamai's 90 day history shows 32 incidents with a median duration of almost 20 hours, so an incident like this sitting open for hours without a close is not unusual for this provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.