Live  /  Linode  /  Incident

Linode: Connectivity Issue between ID-CGK (Jakarta) and SG-SIN-2 (Singapore 2)

Linode · linode.comMinor incidentmonitoring2026-10-29 09:16 UTC
Public — what happened

Summary

Linode said it began investigating a connectivity problem between its Jakarta and Singapore 2 data centers at 13:54 UTC on 2026-10-25. The company said users could see intermittent timeouts and errors on services hosted in the Jakarta data center. By 16:12 UTC Linode said it had corrected the connectivity problems and moved to monitoring, and it asked anyone still affected to open a support ticket. As of its latest update on 2026-10-29, Linode said it was still monitoring to confirm the impact was fully mitigated, and it had not marked the incident resolved.

Affected

ID-CGK (Jakarta), SG-SIN-2 (Singapore 2)

As listed on Linode’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Linode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Linode: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Linode report →

More from Linode

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Linode status & history page.

Related: Linode status & history. SquidGrid is not affiliated with Linode.