Linode favicon

Linode outage on 2026-11-01

linode.com
November 2026 1 Minor incident

Linode's IN-MAA (Chennai) and IN-BOM-2 (Mumbai 2) data centres lost reliable connectivity for 3 hours and 13 minutes on 1 November 2026. Linode says the fault was theirs and resolved it on their own clock, not yours.

Started

16:40 UTC

Duration

Lasted 3h 13m

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 opened an incident at 16:40 UTC naming two data centres, IN-MAA in Chennai and IN-BOM-2 in Mumbai 2, as affected by a connectivity issue. Their own text warned that users could see intermittent connection timeouts and errors across all services deployed in those data centres, which covers compute, storage and anything else hosted there rather than one isolated feature. At 17:23 UTC, 43 minutes in, Linode posted that a fix had been implemented and they were monitoring the results. The incident stayed in that monitoring state for roughly two and a half hours before Linode marked it resolved at 19:52 UTC, giving a total run of 3 hours and 13 minutes. That is three filed updates in total: investigating, monitoring, resolved, and nothing beyond that has been published. No cause is given anywhere in those three updates, so the reason for the connectivity break is not on the record. Linode's status page lists no other components as affected beyond the two named data centres. There are no user reports logged in the window to compare against Linode's own account, so this page rests entirely on what Linode chose to publish. Over the past 90 days Linode has filed 26 incidents with a median duration of 5 hours and 45 minutes, which makes this one shorter than their typical recent incident. Across all time Linode has logged 598 incidents, averaging 7.7 a month, so a connectivity incident in a given month is not unusual for this provider.

Learning

When a cloud provider's data centre loses connectivity, the failure usually sits in their network layer, upstream of anything your own application could check. A check that pings your endpoint from outside tells you whether your product responded at that moment, but it cannot see into Linode's internal routing or peering, so your dashboard can stay green while Linode's own status page is mid-incident. That is exactly the shape of this event: a named infrastructure problem affecting whole data centres, resolved by Linode's team rather than by anything you could have fixed from your side. In our own 30 day tracking of Linode, 15 incidents were logged with only 10 marked resolved and a median duration of 15 hours and 13 minutes, a much longer span than this single 3 hour and 13 minute event, which shows how much incident length varies even within one provider's record. If your product runs on Linode, your own monitoring tells you whether your application is answering requests, and that is only half the picture during an event like this. UptimeRobot now watches the provider's half too, so next time connectivity drops in a data centre like IN-MAA or IN-BOM-2, 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.