Linode favicon

Linode outage on 2026-10-25

linode.com
October 2026 25 Minor incident

Linode's ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) data centres lost connectivity between them starting at 13:54 UTC. If your product runs services split across these two locations, you may have seen intermittent connection timeouts and errors. The fault sits on Linode's network, not yours.

Started

13:54 UTC

Duration

Lasted 22d 4h

Source

IsDown

Next time

Linode 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.

What happened?

Linode's status page opened this incident at 13:54 UTC, reporting a connectivity issue between its ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2) data centres. The initial note warned that users may see intermittent connection timeouts and errors for all services deployed in those two locations. At 14:52 UTC Linode said only that it was continuing to investigate, with no new detail added. By 16:12 UTC the company reported it had corrected the connectivity issue and moved to monitoring, while telling anyone still affected to open a support ticket. A further monitoring note followed one minute later at 16:13 UTC. The most recent update on record came at 09:16 UTC, saying Linode would continue to monitor to ensure the impact had been fully mitigated. That is five updates in total, all from Linode, and none of them states a cause. No components list was published alongside this incident, and no user reports were filed during the window covered here. The incident carries no listed duration and is still open as of that last 09:16 UTC note, meaning Linode has not yet declared it resolved. Over the past 90 days Linode has logged 24 incidents with a median duration of 6 hours 31 minutes, so a multi-hour connectivity problem like this one is not unusual for this provider.

Learning

This incident is a network path problem between two specific data centres, not a failure of the servers inside either one, which is why checks aimed only at your own endpoints inside ID-CGK or SG-SIN-2 could still come back green while traffic crossing between them timed out. Our own 30 day figures for Linode show 12 incidents with only 8 resolved and a median duration of 15h 13m, a pattern that lines up with how this incident has unfolded: quick to appear, slow to get a final close-out note. If your architecture depends on cross-region calls, replication, or failover between Jakarta and Singapore, that is exactly the layer this kind of fault hits, and it sits below anything your own health checks are built to see. Watching your own application tells you whether your code is running, not whether the network path between the data centres it depends on is intact. That gap is why an external view of the provider's own infrastructure matters alongside your internal monitoring. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.