Linode had a 4h 27m incident on 5 November 2026 that stopped migrations and booting for some hosts across all regions. The fault sat on Linode's side of the infrastructure, not in anything you configured.
Started
12:58 UTC
Duration
Lasted 4h 27m
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.
Affected components: Linode.com
What happened?
Linode's status page shows one incident on this day, titled "Emerging Host Issue", opened at 12:58 UTC. The first update said the team was investigating issues affecting migrations and booting for some hosts across all regions, which points at a problem in the host fleet rather than a single data centre. At 14:03 UTC Linode said the issue had been identified and a fix was being implemented, still without saying what the underlying cause was. The incident was marked resolved at 17:23 UTC, with Linode stating the actual fix had taken hold by 14:09 UTC and the gap was spent monitoring to confirm it held. That gives a total of three updates across 4 hours and 27 minutes, and Linode's own account is the only record of what happened, there is no separate post-mortem on this incident. Linode.com is the one component listed against the incident. No user reports were filed in the window covered by this page. Linode did not say how many hosts or regions were affected, only that it was "some hosts across all regions", so the scope stays vague by the vendor's own wording. There's no explanation on record for why booting and migrations specifically were hit rather than running instances. If you had a server already running during this window, this incident on its own gives no reason to expect it went down, since boot and migration operations are a different code path from a live instance staying up.
Learning
This incident sat in Linode's host and migration layer, the part of the stack that handles booting a server or moving it between physical hosts, not the part that keeps an already-running instance reachable. An external check that only pings your running server's IP address would have stayed green through this whole thing, because that server was never the thing that broke. Over the last 30 days UptimeRobot recorded 16 incidents against Linode with a median duration of 15h 13m, far longer than the 4h 27m seen here, and only 12 of those 16 show as resolved, which tells you how much can be happening at the infrastructure layer while your own uptime graph shows nothing unusual. The 90 day history shows 28 incidents with a median duration of 5 hours 43 minutes, so an outage in this length range is ordinary for Linode, not exceptional. If your product depends on provisioning new instances, migrating existing ones, or rebooting on demand, a window like this one would have hit you even while your running fleet looked fine from the outside. The lesson is to watch the provider's operational layer separately from your own endpoints, since they fail independently and a green check on your side tells you nothing about the other side. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.