Skip to content

Linode status · linode.com

Is Linode Down Today?

Akamai Linode cloud hosting.

Report an issue

No, Linode is not down

linode.com is currently up. Our monitoring probes can reach linode.com and complete a check without errors. Latest response time was 1226 ms. The latest automated check was run 2026-08-14 18:19 UTC from primary location.

Current status
Operational

Currently up for 2h 30m

Last check
Checked every 3 minutes

Latest 2026-08-14 18:19 UTC · Primary location

Last 24 hours
100%

2 incidents, 2d down

Official status
Operational
Our check
Operational
Active incident
Upstream Issues - Ubuntu
Last outage
2026-08-10
Response time
1226 ms
User reports
Normal

None today

Linode live status

250 of 250 operational

  • Akamai Cloud Pulse (ACLP) - AlertsOperational
  • Akamai Cloud Pulse (ACLP) - LogsOperational
  • Akamai Cloud Pulse (ACLP) - MetricsOperational
  • AP-Northeast (Tokyo 2) Linode Kubernetes EngineOperational
  • AP-Northeast-2 (Tokyo 2)Operational
  • AP-Northeast-2 (Tokyo 2)Operational
  • AP-Northeast-2 (Tokyo 2) BackupsOperational
  • AP-Northeast-2 (Tokyo 2) Block StorageOperational
  • AP-Northeast-2 (Tokyo 2) NodeBalancersOperational
  • AP-South (Singapore)Operational
  • AP-South (Singapore)Operational
  • AP-South (Singapore) BackupsOperational
  • AP-South (Singapore) Block StorageOperational
  • AP-South (Singapore) Linode Kubernetes EngineOperational
  • AP-South (Singapore) NodeBalancersOperational
  • AP-South (Singapore) Object StorageOperational
  • AP-Southeast (Sydney)Operational
  • AP-Southeast (Sydney)Operational
  • AP-Southeast (Sydney) BackupsOperational
  • AP-Southeast (Sydney) Block StorageOperational
  • AP-Southeast (Sydney) Linode Kubernetes EngineOperational
  • AP-Southeast (Sydney) NodeBalancersOperational
  • AP-West (Mumbai)Operational
  • AP-West (Mumbai)Operational
  • AP-West (Mumbai) BackupsOperational
  • AP-West (Mumbai) Block StorageOperational
  • AP-West (Mumbai) Linode Kubernetes EngineOperational
  • AP-West (Mumbai) NodeBalancersOperational
  • AU-MEL (Melbourne)Operational
  • AU-MEL (Melbourne)Operational
  • AU-MEL (Melbourne)Operational
  • AU-MEL (Melbourne) BackupsOperational
  • AU-MEL (Melbourne) Block StorageOperational
  • AU-MEL (Melbourne) Linode Kubernetes EngineOperational
  • AU-MEL (Melbourne) NodeBalancersOperational
  • AU-MEL (Melbourne) Object StorageOperational
  • BackupsOperational
  • Block StorageOperational
  • BR-GRU (São Paulo)Operational
  • BR-GRU (São Paulo)Operational
  • BR-GRU (São Paulo) Linode Kubernetes EngineOperational
  • BR-GRU (São Paulo) BackupsOperational
  • BR-GRU (São Paulo) Block StorageOperational
  • BR-GRU (São Paulo) NodeBalancersOperational
  • BR-GRU (Sao Paulo) Object StorageOperational
  • CA-Central (Toronto)Operational
  • CA-Central (Toronto)Operational
  • CA-Central (Toronto) BackupsOperational
  • CA-Central (Toronto) Block StorageOperational
  • CA-Central (Toronto) Linode Kubernetes EngineOperational
  • CA-Central (Toronto) NodeBalancersOperational
  • CL-SCL (Santiago)Operational
  • CL-SCL (Santiago)Operational
  • Cloud Manager and APIOperational
  • CO-BOG (Bogota)Operational
  • CO-BOG (Bogota)Operational
  • DE-FRA-2 (Frankfurt 2)Operational
  • DE-FRA-2 (Frankfurt 2)Operational
  • DE-FRA-2 (Frankfurt 2) BackupsOperational
  • DE-FRA-2 (Frankfurt 2) Block StorageOperational
  • DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineOperational
  • DE-FRA-2 (Frankfurt 2) NodeBalancersOperational
  • DE-FRA-2 (Frankfurt 2) Object StorageOperational
  • DE-HAM (Hamburg)Operational
  • DE-HAM (Hamburg)Operational
  • ES-MAD (Madrid)Operational
  • ES-MAD (Madrid)Operational
  • ES-MAD (Madrid) BackupsOperational
  • ES-MAD (Madrid) Block StorageOperational
  • ES-MAD (Madrid) Linode Kubernetes EngineOperational
  • ES-MAD (Madrid) NodeBalancersOperational
  • ES-MAD (Madrid) Object StorageOperational
  • EU-Central (Frankfurt)Operational
  • EU-Central (Frankfurt)Operational
  • EU-Central (Frankfurt) NodeBalancersOperational
  • EU-Central (Frankfurt) BackupsOperational
  • EU-Central (Frankfurt) Block StorageOperational
  • EU-Central (Frankfurt) Linode Kubernetes EngineOperational
  • EU-Central (Frankfurt) Object StorageOperational
  • EU-West (London)Operational
  • EU-West (London)Operational
  • EU-West (London) BackupsOperational
  • EU-West (London) Block StorageOperational
  • EU-West (London) Linode Kubernetes EngineOperational
  • EU-West (London) NodeBalancersOperational
  • FR-MRS (Marseille)Operational
  • FR-MRS (Marseille)Operational
  • FR-PAR (Paris)Operational
  • FR-PAR (Paris)Operational
  • FR-PAR (Paris) BackupsOperational
  • FR-PAR (Paris) Block StorageOperational
  • FR-PAR (Paris) Linode Kubernetes EngineOperational
  • FR-PAR (Paris) NodeBalancersOperational
  • FR-PAR (Paris) Object StorageOperational
  • FR-PAR-2 (Paris 2)Operational
  • GB-LON (London 2)Operational
  • GB-LON (London 2)Operational
  • GB-LON (London 2)Operational
  • GB-LON (London 2) BackupsOperational
  • GB-LON (London 2) Block StorageOperational
  • GB-LON (London 2) Linode Kubernetes EngineOperational
  • GB-LON (London 2) NodeBalancersOperational
  • GB-LON (London 2) Object StorageOperational
  • Hosted DNS ServiceOperational
  • ID-CGK (Jakarta)Operational
  • ID-CGK (Jakarta)Operational
  • ID-CGK (Jakarta) BackupsOperational
  • ID-CGK (Jakarta) Block StorageOperational
  • ID-CGK (Jakarta) Linode Kubernetes EngineOperational
  • ID-CGK (Jakarta) NodeBalancersOperational
  • ID-CGK (Jakarta) Object StorageOperational
  • IN-BOM-2 (Mumbai 2)Operational
  • IN-BOM-2 (Mumbai 2)Operational
  • IN-BOM-2 (Mumbai 2) BackupsOperational
  • IN-BOM-2 (Mumbai 2) Block StorageOperational
  • IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineOperational
  • IN-BOM-2 (Mumbai 2) NodeBalancersOperational
  • IN-BOM-2 (Mumbai 2) Object StorageOperational
  • IN-MAA (Chennai)Operational
  • IN-MAA (Chennai)Operational
  • IN-MAA (Chennai) BackupsOperational
  • IN-MAA (Chennai) Block StorageOperational
  • IN-MAA (Chennai) Linode Kubernetes EngineOperational
  • IN-MAA (Chennai) NodeBalancersOperational
  • IN-MAA (Chennai) Object StorageOperational
  • IT-MIL (Milan)Operational
  • IT-MIL (Milan)Operational
  • IT-MIL (Milan) BackupsOperational
  • IT-MIL (Milan) Block StorageOperational
  • IT-MIL (Milan) Linode Kubernetes EngineOperational
  • IT-MIL (Milan) NodeBalancersOperational
  • IT-MIL (Milan) Object StorageOperational
  • JP-OSA (Osaka)Operational
  • JP-OSA (Osaka)Operational
  • JP-OSA (Osaka) BackupsOperational
  • JP-OSA (Osaka) Block StorageOperational
  • JP-OSA (Osaka) Linode Kubernetes EngineOperational
  • JP-OSA (Osaka) NodeBalancersOperational
  • JP-OSA (Osaka) Object StorageOperational
  • JP-TYO-3 (Tokyo 3)Operational
  • JP-TYO-3 (Tokyo 3)Operational
  • JP-TYO-3 (Tokyo 3) Block StorageOperational
  • JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineOperational
  • JP-TYO-3 (Tokyo 3) NodeBalancersOperational
  • JP-TYO-3 (Tokyo 3) Object StorageOperational
  • JP-TYO-3 (Tokyo) BackupsOperational
  • Linode Kubernetes EngineOperational
  • Linode.comOperational
  • LongviewOperational
  • Managed DatabasesOperational
  • Metadata ServiceOperational
  • MX-QRO (Queretaro)Operational
  • MX-QRO (Queretaro)Operational
  • MY-KUL (Kuala Lumpur)Operational
  • MY-KUL (Kuala Lumpur)Operational
  • NL-AMS (Amsterdam)Operational
  • NL-AMS (Amsterdam)Operational
  • NL-AMS (Amsterdam) BackupsOperational
  • NL-AMS (Amsterdam) Block StorageOperational
  • NL-AMS (Amsterdam) Linode Kubernetes EngineOperational
  • NL-AMS (Amsterdam) NodeBalancersOperational
  • NL-AMS (Amsterdam) Object StorageOperational
  • NodeBalancersOperational
  • NZ-AKL (Auckland)Operational
  • NZ-AKL (Auckland)Operational
  • Object StorageOperational
  • ObservabilityOperational
  • RegionsOperational
  • SE-STO (Stockholm)Operational
  • SE-STO (Stockholm)Operational
  • SE-STO (Stockholm) BackupsOperational
  • SE-STO (Stockholm) Block StorageOperational
  • SE-STO (Stockholm) Linode Kubernetes EngineOperational
  • SE-STO (Stockholm) NodeBalancersOperational
  • SE-STO (Stockholm) Object StorageOperational
  • SG-SIN-2 (Singapore 2)Operational
  • SG-SIN-2 (Singapore 2)Operational
  • SG-SIN-2 (Singapore 2) BackupsOperational
  • SG-SIN-2 (Singapore 2) Block StorageOperational
  • SG-SIN-2 (Singapore 2) Linode Kubernetes EngineOperational
  • SG-SIN-2 (Singapore 2) NodeBalancersOperational
  • SG-SIN-2 (Singapore 2) Object StorageOperational
  • US-Central (Dallas)Operational
  • US-Central (Dallas)Operational
  • US-Central (Dallas) BackupsOperational
  • US-Central (Dallas) Block StorageOperational
  • US-Central (Dallas) Linode Kubernetes EngineOperational
  • US-Central (Dallas) NodeBalancersOperational
  • US-DEN (Denver)Operational
  • US-DEN (Denver)Operational
  • US-East (Newark)Operational
  • US-East (Newark)Operational
  • US-East (Newark) BackupsOperational
  • US-East (Newark) Block StorageOperational
  • US-East (Newark) Linode Kubernetes EngineOperational
  • US-East (Newark) NodeBalancersOperational
  • US-East (Newark) Object StorageOperational
  • US-HOU (Houston)Operational
  • US-HOU (Houston)Operational
  • US-IAD (Washington)Operational
  • US-IAD (Washington)Operational
  • US-IAD (Washington) BackupsOperational
  • US-IAD (Washington) Block StorageOperational
  • US-IAD (Washington) Linode Kubernetes EngineOperational
  • US-IAD (Washington) NodeBalancersOperational
  • US-IAD (Washington) Object StorageOperational
  • US-IAD-2 (Washington 2)Operational
  • US-LAX (Los Angeles)Operational
  • US-LAX (Los Angeles)Operational
  • US-LAX (Los Angeles) BackupsOperational
  • US-LAX (Los Angeles) Block StorageOperational
  • US-LAX (Los Angeles) Linode Kubernetes EngineOperational
  • US-LAX (Los Angeles) NodeBalancersOperational
  • US-LAX (Los Angeles) Object StorageOperational
  • US-MIA (Miami)Operational
  • US-MIA (Miami)Operational
  • US-MIA (Miami) BackupsOperational
  • US-MIA (Miami) Block StorageOperational
  • US-MIA (Miami) Linode Kubernetes EngineOperational
  • US-MIA (Miami) NodeBalancersOperational
  • US-MIA (Miami) Object StorageOperational
  • US-ORD (Chicago)Operational
  • US-ORD (Chicago)Operational
  • US-ORD (Chicago) BackupsOperational
  • US-ORD (Chicago) Block StorageOperational
  • US-ORD (Chicago) Linode Kubernetes EngineOperational
  • US-ORD (Chicago) NodeBalancersOperational
  • US-ORD (Chicago) Object StorageOperational
  • US-SEA (Seattle)Operational
  • US-SEA (Seattle)Operational
  • US-SEA (Seattle) BackupsOperational
  • US-SEA (Seattle) Block StorageOperational
  • US-SEA (Seattle) Linode Kubernetes EngineOperational
  • US-SEA (Seattle) NodeBalancersOperational
  • US-SEA (Seattle) Object StorageOperational
  • US-Southeast (Atlanta)Operational
  • US-Southeast (Atlanta)Operational
  • US-Southeast (Atlanta) BackupsOperational
  • US-Southeast (Atlanta) Block StorageOperational
  • US-Southeast (Atlanta) Linode Kubernetes EngineOperational
  • US-Southeast (Atlanta) NodeBalancersOperational
  • US-Southeast (Atlanta) Object StorageOperational
  • US-West (Fremont)Operational
  • US-West (Fremont)Operational
  • US-West (Fremont) BackupsOperational
  • US-West (Fremont) Block StorageOperational
  • US-West (Fremont) Linode Kubernetes EngineOperational
  • US-West (Fremont) NodeBalancersOperational
  • ZA-JNB (Johannesburg)Operational
  • ZA-JNB (Johannesburg)Operational

Current incidents

  • Upstream Issues - Ubuntu

    IdentifiedOperational

    We have identified the cause of the issue, and a fix is being implemented. We will provide an update as soon as the solution is in place.

    Started · 2026-08-10 17:15 UTC

    Official incident update
    1. 2026-08-10 17:15 UTCInvestigating

      Our team is investigating an upstream issue impacting Ubuntu deployments. This may impact the ability to install package and security updates on all Ubuntu systems.

    2. 2026-08-11 23:35 UTCInvestigating

      We are continuing to investigate this issue. The appropriate subject matter experts are engaged. Subsequent updates around mitigation status will be posted as progress is made.

    3. 2026-08-12 03:29 UTCIdentified

      We have identified the cause of the issue, and a fix is being implemented. We will provide an update as soon as the solution is in place.

  • Service Issue - GPU and VPU Booting issues

    IdentifiedPossible issues

    We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    Started · 2025-12-03 15:15 UTC

    Official incident update
    1. 2025-12-03 15:15 UTCInvestigating

      Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.

    2. 2025-12-03 16:48 UTCIdentified

      Our team has identified the issue affecting booting up GPU and VPU plans. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

    3. 2025-12-04 20:51 UTCIdentified

      We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.

    4. 2025-12-17 13:40 UTCIdentified

      We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.

    5. 2026-01-05 17:16 UTCIdentified

      We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.

    6. 2026-01-05 19:30 UTCIdentified

      We have successfully identified a solution to address the issue at hand. We are currently in the testing phase prior to initiating the rollout of the fix. Further updates regarding the status of the mitigation efforts will be provided as progress is made.

    7. 2026-02-03 15:34 UTCIdentified

      We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.

    8. 2026-02-19 16:41 UTCIdentified

      We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.

    9. 2026-02-26 15:42 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    10. 2026-03-19 20:13 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    11. 2026-04-06 13:39 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    12. 2026-04-15 15:12 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    13. 2026-05-13 20:59 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    14. 2026-05-26 21:17 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

    15. 2026-07-03 13:55 UTCIdentified

      We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.

Response time

Latest 714 ms

Loading response-time chart…

Uptime

Availability from independent checks, with recorded incidents and downtime in each window.

Today

100%

2 incidents, 1d 12h down

Last 7 days

100%

2 incidents, 11d 1h down

Last 30 days

100%

2 incidents, 34d 1h down

Last 365 days

100%

2 incidents, 258d 4h down

Latest Linode incidents

Recorded outages with duration and start time.

Last recorded 2026-08-10 17:15 UTC

IncidentDurationStarted

Upstream Issues - Ubuntu

Identified
Ongoing2026-08-10 17:15 UTC

Service Issue - GPU and VPU Booting issues

Identified
Ongoing2025-12-03 15:15 UTC

How this status checker works

Who's Down Today monitors Linode independently of the company that runs it. We send reachability checks from our primary location every 3 minutes and record response time, HTTP errors, and timeouts.

When Linode publishes a public status page or incident feed, that official signal is treated as a strong input and is shown separately from our probe. A failed check from one location can be regional, caused by bot protection, or a transient network issue. We prefer "status uncertain" over a false major outage.

This page can show when an issue started, how long it lasted, and the type of error observed. It cannot see internal systems, so it does not claim a private root cause unless the provider publishes one. Read the full methodology.

Frequently asked questions

Is Linode down right now?

No. No, Linode is not down. Who's Down Today shows Linode as operational based on the latest official signals and independent checks. If you still cannot reach linode.com, the issue may be local to your connection, DNS, VPN, browser, or device.

Is Linode down for everyone or just me?

Who's Down Today currently shows Linode as operational from our monitoring location, which means linode.com is responding normally to our checks. If you are still having trouble, try another browser, device, or network, and check DNS or VPN settings.

What should I do if linode.com is up but I still cannot access it?

Try opening linode.com from another browser, device, or network (for example a mobile hotspot). You can also disable a VPN, flush local DNS, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Linode outage.

How does Who's Down Today check if Linode is down?

We combine independent HTTP reachability checks with public status information where it exists. When Linode publishes a public status page or incident feed, that official signal is treated as a strong input. A single failed probe is treated as a possible transient or regional failure, not an automatic global outage. Bot protection, geo restrictions, and HTTP 403 responses are not automatically classified as downtime.

What does a Linode outage mean?

An outage on this page means recorded incidents or failed checks indicated that Linode was not responding normally. That does not always mean every user was affected. Some outages are regional, some affect only certain features, and some appear as errors or slow responses instead of a full failure.

Can this page tell me the root cause of a Linode outage?

Not exactly. We can show when an issue started, how long it lasted, the public incident title, and symptoms such as timeouts or slow response times. We do not have access to Linode's internal systems, so we cannot identify a private root cause such as a failed deploy or database incident unless the provider publishes it.

How do I report an issue with Linode?

Use the report form on this page if Linode looks down for you. Reports are anonymous, rate-limited, and used only as supporting evidence alongside official sources and independent checks.