Is Linode Down?

No — Linode is up

Reachable from all 8 checked regions

Average response time: 322ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.linode.com

Linode uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

202ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 14 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

14-day clean streak

Jul 19 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr

82ms

DNS 0ms TCP 1ms TLS 11ms TTFB 81ms

fra

502ms

DNS 0ms TCP 98ms TLS 198ms TTFB 499ms

gru

54ms

DNS 0ms TCP 2ms TLS 10ms TTFB 53ms

iad

122ms

DNS 3ms TCP 1ms TLS 9ms TTFB 121ms

jnb

320ms

DNS 0ms TCP 0ms TLS 5ms TTFB 318ms

lax

64ms

DNS 0ms TCP 1ms TLS 6ms TTFB 62ms

lhr

37ms

DNS 0ms TCP 4ms TLS 7ms TTFB 35ms

nrt

1377ms

DNS 0ms TCP 271ms TLS 546ms TTFB 1373ms

ord

103ms

DNS 0ms TCP 12ms TLS 15ms TTFB 102ms

What Linode does

Linode, now part of Akamai, provides virtual servers, managed databases, DNS hosting and object storage across data centres in North America, Europe and Asia. Developers and small teams run application servers and databases on it directly, so an incident in one facility takes down whatever is hosted there rather than degrading a shared service everyone notices at once.

What an outage looks like

Servers in one data centre become unreachable while everything in other regions runs normally, which is the usual shape of a Linode incident. The Cloud Manager may not load, or may load without being able to reboot or rebuild an instance. Hosted DNS may stop answering, which breaks name resolution for domains using Linode nameservers even when the servers themselves are healthy.

What to do about it

Check status.linode.com, which lists each data centre as its own component, including Newark, Dallas, Fremont, Atlanta, Washington, Chicago, Toronto, London, Frankfurt, Paris and Singapore, alongside Cloud Manager and API, Hosted DNS Service and Managed Databases. Identify your instance region first, because a green banner elsewhere is irrelevant. If Cloud Manager is down but your server is up, avoid rebuilding anything until the control plane is trustworthy again.

Is it down for everyone, or just you?

If this page says Linode is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

DigitalOcean

AWS

Fly.io

Render

Linode outage FAQ

Is my server affected if Linode reports an incident?

Only if it is in the affected data centre. Linode lists every region as a separate component precisely because incidents are usually facility-specific: an issue in Frankfurt says nothing about Newark. Find your instance region in Cloud Manager, then read that component rather than the overall banner. This is the first thing to establish, because it determines whether you have a problem at all.

Does a Cloud Manager outage mean my servers are down?

No. Cloud Manager and the API form the control plane, and they are listed separately from the regions for that reason. Running instances keep serving traffic while the dashboard is unavailable; what you lose is the ability to reboot, resize, rebuild or provision. If you have SSH access, you can usually still administer the machine directly during a control plane incident.

What happens to my domains if Linode DNS goes down?

Domains using Linode nameservers may stop resolving, which looks like a total outage to visitors even though the servers behind them are healthy. Hosted DNS Service is a separate component. Resolvers cache records for the TTL you set, so a short incident may pass largely unnoticed on a long TTL, while an aggressively short TTL exposes you faster. This is worth reviewing before the next incident.

Should I migrate to another region during an outage?

Rarely worth it mid-incident. Rebuilding in a new region means provisioning, restoring data and repointing DNS, which usually takes longer than the incident and leaves you with split state to reconcile. It is a reasonable move only if you already keep current backups or images in a second region. Otherwise the faster path is to wait and use the incident to justify that preparation afterwards.

How we measure this

We request Linode's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Linode publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Linode goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required