Live  /  Linode  /  Incident

Linode: Connectivity Issue - IN-MAA and IN-BOM-2

Linode · linode.comResolved2026-11-01 19:52 UTC
Public — what happened

Summary

Linode said it began investigating a connectivity problem at 16:40 UTC on 2026-11-01 affecting its Chennai (IN-MAA) and Mumbai 2 (IN-BOM-2) data centers. The company said users of services in those locations might see intermittent timeouts and errors. At 17:23 UTC Linode reported that a fix had been put in place and that it was watching the results, and the incident was marked resolved at 19:52 UTC. No cause was given in the text provided.

Affected

IN-MAA (Chennai), IN-BOM-2 (Mumbai 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 45, 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.