Linode favicon

Linode outage on 2026-11-02

linode.com
November 2026 2 Minor incident

Linode's FR-PAR-2 data centre in Paris had a connectivity problem lasting 2h 53m on 2 November 2026. If your workloads sit in that data centre, this was Linode's fault, not yours.

Started

18:03 UTC

Duration

Lasted 2h 53m

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 18:03 UTC saying its team was investigating a connectivity issue affecting its FR-PAR-2 data centre in Paris. The notice warned that users may see intermittent connection timeouts and errors for all services deployed in that data centre, which covers anything hosted there, not just one product line. A follow-up at 18:18 UTC simply said the team was continuing to investigate, with no new detail on scope or cause. The incident stayed in that state for over two and a half hours before Linode posted a resolution at 20:53 UTC, saying it had not observed any additional connectivity issues and was considering the matter closed. Linode's own status page is the only source here, and it never named a root cause at any point in the three updates filed. No user reports were logged in the window on this page, so there is no independent account of what connection failures actually looked like from outside Linode's network. The record lists no specific components as affected beyond the FR-PAR-2 data centre itself, and there is no breakdown by service. Over the past 90 days Linode has logged 27 incidents with a median duration of 5 hours 45 minutes, so this one resolved faster than Linode's typical recent incident. Across all time Linode has filed 599 incidents at a rate of about 7.7 per month, which puts a single-datacentre connectivity problem well within its normal pattern rather than anything exceptional.

Learning

This incident was a network layer problem inside one Linode data centre, the kind of fault that sits upstream of anything you control in your own application. If your monitoring checks your endpoints directly, a connectivity issue at the data centre level can produce timeouts and errors that look like your problem even though nothing in your code or configuration changed. Linode's status page described the symptom as intermittent, which means some requests may have succeeded while others failed, a pattern that is easy to misdiagnose as a flaky dependency rather than a provider-side network fault. There is no breakdown here of which services inside FR-PAR-2 were hit hardest, so if you run in that region you are relying on Linode's own account of scope. The gap between a provider's status page and what you see from your own monitoring is exactly why checking from outside the provider's network matters, since 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.