Linode Outage History

Linode is up right now

Linode had 67 outages in the last 2 years totaling 618h 22m of downtime — averaging 2.8 incidents per month.

There were 67 Linode outages since November 8, 2025 totaling 618h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.linode.com

Notice June 16, 2026

Emerging Service Issue - Networking - US-MIA (Miami)

Detected by Pingoru
Jun 16, 2026, 02:29 PM UTC
Resolved
Jun 16, 2026, 05:18 PM UTC
Duration
2h 49m
Affected: US-MIA (Miami)
Timeline · 2 updates
  1. investigating Jun 16, 2026, 02:29 PM UTC

    Our team is investigating an emerging service issue affecting networking in US-MIA (Miami). We will share additional updates as we have more information.

  2. resolved Jun 16, 2026, 05:18 PM UTC

    We haven’t observed any additional connectivity issues in our US-MIA (Miami) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Notice June 16, 2026

Emerging Service Issue - Linode Migrations

Detected by Pingoru
Jun 16, 2026, 03:44 AM UTC
Resolved
Jun 16, 2026, 06:06 AM UTC
Duration
2h 22m
Timeline · 3 updates
  1. identified Jun 16, 2026, 03:44 AM UTC

    Our team is investigating an emerging service issue affecting Linode Migrations in all regions. Migrations might be slow or pending for long time. We will share additional updates as we have more information.

  2. monitoring Jun 16, 2026, 05:14 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 16, 2026, 06:06 AM UTC

    The issue affecting Linode Migrations has been resolved. Resize and Migration operations should be operating as normal now.

Read the full incident report →

Notice June 5, 2026

Emerging Service Issue - LKE Enterprise - All Regions

Detected by Pingoru
Jun 05, 2026, 02:23 PM UTC
Resolved
Jun 05, 2026, 02:58 PM UTC
Duration
35m
Affected: US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes EngineAP-South (Singapore) Linode Kubernetes EngineAP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineES-MAD (Madrid) Linode Kubernetes EngineIT-MIL (Milan) Linode Kubernetes EngineUS-MIA (Miami) Linode Kubernetes EngineUS-LAX (Los Angeles) Linode Kubernetes EngineGB-LON (London 2) Linode Kubernetes EngineAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Timeline · 2 updates
  1. investigating Jun 05, 2026, 02:23 PM UTC

    We are currently investigating an emerging service issue affecting LKE Enterprise clusters across all regions. During this time, users may experience failures when deploying new clusters or upgrading existing ones. Our team is working to resolve this, and we will provide updates here as they become available.

  2. resolved Jun 05, 2026, 02:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

Emerging Service Issue - Support Phone Line

Detected by Pingoru
Jun 03, 2026, 02:22 PM UTC
Resolved
Jun 04, 2026, 03:51 PM UTC
Duration
1d 1h
Timeline · 3 updates
  1. investigating Jun 03, 2026, 02:22 PM UTC

    Our team is investigating an upstream emerging service issue affecting our Support phone line due to problems with an upstream provider. We will share additional updates as we have more information. If you are having difficulty reaching us over the phone during this time, please reach us through a ticket.

  2. investigating Jun 03, 2026, 06:33 PM UTC

    Our team is continuing to investigate an upstream service issue affecting our Support phone line. While stability of the service has improved, we have not yet identified the cause of the issue. We will share additional updates as we have more information. If you are having difficulty reaching us over the phone during this time, please open a Support ticket from the Cloud Manager.

  3. resolved Jun 04, 2026, 03:51 PM UTC

    The upstream issue has been resolved, and our Support phone line should now be fully functional again.

Read the full incident report →

Minor June 3, 2026

Service Issue - Block Storage Newark, US

Detected by Pingoru
Jun 03, 2026, 08:58 AM UTC
Resolved
Jun 04, 2026, 09:11 AM UTC
Duration
1d
Affected: US-East (Newark) Block Storage
Timeline · 7 updates
  1. investigating Jun 03, 2026, 08:58 AM UTC

    Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.

  2. investigating Jun 03, 2026, 10:53 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 03, 2026, 11:25 AM UTC

    At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

  4. investigating Jun 03, 2026, 12:55 PM UTC

    Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.

  5. monitoring Jun 03, 2026, 03:44 PM UTC

    At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

  6. resolved Jun 04, 2026, 09:11 AM UTC

    We haven’t observed any additional issues with the Block Storage service in Newark, US, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

  7. postmortem Jun 04, 2026, 12:55 PM UTC

    Between 22:50 UTC on June 2, 2026 and 19:00 UTC on June 3, 2026, some customers experienced intermittent performance degradation and long access times when interacting with the Compute Block Storage cluster in Newark, US. During this period, intermittent component instability triggered intensive background recovery operations. This elevated system load resulted in a temporary degradation of data redundancy, higher read/write latency, and reduced throughput for the affected volumes. To mitigate the impact, Akamai successfully restored the affected storage drives to operation, stabilizing the cluster and eliminating active customer impact. Following this, additional actions aim to fully restore standard system redundancy. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Read the full incident report →

Notice May 16, 2026

Service Issue - [Linodes and Linode Kubernetes Engine (LKE)] - [All Regions]

Detected by Pingoru
May 16, 2026, 12:42 AM UTC
Resolved
May 16, 2026, 01:43 AM UTC
Duration
1h 1m
Affected: US-East (Newark)US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas)US-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont)US-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta)US-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington)US-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago)US-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto)CA-Central (Toronto) Linode Kubernetes EngineEU-West (London)EU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt)EU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris)FR-PAR (Paris) Linode Kubernetes EngineAP-South (Singapore)AP-South (Singapore) Linode Kubernetes EngineAP-Northeast-2 (Tokyo 2)AP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai)AP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney)AP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm)SE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle)US-SEA (Seattle) Linode Kubernetes EngineIT-MIL (Milan)JP-OSA (Osaka) Linode Kubernetes EngineJP-OSA (Osaka)IN-MAA (Chennai) Linode Kubernetes EngineIN-MAA (Chennai)ID-CGK (Jakarta) Linode Kubernetes EngineID-CGK (Jakarta)BR-GRU (São Paulo) Linode Kubernetes EngineBR-GRU (São Paulo)NL-AMS (Amsterdam) Linode Kubernetes EngineNL-AMS (Amsterdam)ES-MAD (Madrid) Linode Kubernetes EngineUS-MIA (Miami)IT-MIL (Milan) Linode Kubernetes EngineUS-LAX (Los Angeles)US-MIA (Miami) Linode Kubernetes EngineES-MAD (Madrid)US-LAX (Los Angeles) Linode Kubernetes EngineAU-MEL (Melbourne)GB-LON (London 2) Linode Kubernetes EngineGB-LON (London 2)AU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2)IN-BOM-2 (Mumbai 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2)DE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2)SG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3)JP-TYO-3 (Tokyo 3) Linode Kubernetes EngineZA-JNB (Johannesburg)NZ-AKL (Auckland)CO-BOG (Bogota)US-DEN (Denver)DE-HAM (Hamburg)US-HOU (Houston)MY-KUL (Kuala Lumpur)FR-MRS (Marseille)MX-QRO (Queretaro)CL-SCL (Santiago)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Timeline · 5 updates

Read the full incident report →

Minor May 13, 2026

Connectivity Issue - NL-AMS

Detected by Pingoru
May 13, 2026, 09:42 AM UTC
Resolved
May 13, 2026, 02:37 PM UTC
Duration
4h 54m
Affected: NL-AMS (Amsterdam)
Timeline · 3 updates
  1. investigating May 13, 2026, 09:42 AM UTC

    Our team is investigating an issue affecting connectivity in our NL-AMS data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. We will share additional updates as we have more information.

  2. monitoring May 13, 2026, 10:44 AM UTC

    At this time we have been able to confirm that no customers should be impacted by the issues affecting connectivity in our NL-AMS data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

  3. resolved May 13, 2026, 02:37 PM UTC

    We haven’t observed any additional connectivity issues in our NL-AMS data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Minor May 1, 2026

(Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]

Detected by Pingoru
May 01, 2026, 05:51 PM UTC
Resolved
May 05, 2026, 10:19 PM UTC
Duration
4d 4h
Affected: US-East (Newark)US-East (Newark) Block StorageUS-East (Newark) NodeBalancersUS-East (Newark) BackupsUS-East (Newark) Object StorageUS-East (Newark) Linode Kubernetes EngineUS-Central (Dallas)US-Central (Dallas) Block StorageUS-Central (Dallas) NodeBalancersUS-Central (Dallas) BackupsUS-Central (Dallas) Linode Kubernetes EngineUS-Southeast (Atlanta) Object StorageUS-West (Fremont)US-West (Fremont) Block StorageUS-West (Fremont) NodeBalancersUS-West (Fremont) BackupsUS-West (Fremont) Linode Kubernetes EngineUS-IAD (Washington) Object StorageUS-Southeast (Atlanta)US-Southeast (Atlanta) NodeBalancersUS-Southeast (Atlanta) BackupsUS-Southeast (Atlanta) Block StorageUS-Southeast (Atlanta) Linode Kubernetes EngineUS-ORD (Chicago) Object StorageEU-Central (Frankfurt) Object StorageUS-IAD (Washington)US-IAD (Washington) BackupsUS-IAD (Washington) Block StorageUS-IAD (Washington) NodeBalancersUS-IAD (Washington) Linode Kubernetes EngineAP-South (Singapore) Object StorageUS-ORD (Chicago)US-ORD (Chicago) BackupsUS-ORD (Chicago) Block StorageUS-ORD (Chicago) NodeBalancersUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto)CA-Central (Toronto) Block StorageCA-Central (Toronto) NodeBalancersCA-Central (Toronto) BackupsCA-Central (Toronto) Linode Kubernetes EngineFR-PAR (Paris) Object StorageEU-West (London)EU-West (London) Block StorageEU-West (London) NodeBalancersEU-West (London) BackupsEU-West (London) Linode Kubernetes EngineSE-STO (Stockholm) Object StorageEU-Central (Frankfurt)EU-Central (Frankfurt) Block StorageEU-Central (Frankfurt) NodeBalancersEU-Central (Frankfurt) BackupsEU-Central (Frankfurt) Linode Kubernetes EngineUS-SEA (Seattle) Object StorageFR-PAR (Paris)FR-PAR (Paris) BackupsFR-PAR (Paris) Block StorageFR-PAR (Paris) NodeBalancersFR-PAR (Paris) Linode Kubernetes EngineJP-OSA (Osaka) Object StorageAP-South (Singapore)AP-South (Singapore) Block StorageAP-South (Singapore) NodeBalancersAP-South (Singapore) BackupsAP-South (Singapore) Linode Kubernetes EngineIN-MAA (Chennai) Object StorageAP-Northeast-2 (Tokyo 2)AP-Northeast-2 (Tokyo 2) NodeBalancersAP-Northeast-2 (Tokyo 2) BackupsAP-Northeast-2 (Tokyo 2) Block StorageAP-Northeast (Tokyo 2) Linode Kubernetes EngineID-CGK (Jakarta) Object StorageAP-West (Mumbai)AP-West (Mumbai) Block StorageAP-West (Mumbai) NodeBalancersAP-West (Mumbai) BackupsAP-West (Mumbai) Linode Kubernetes EngineBR-GRU (Sao Paulo) Object StorageAP-Southeast (Sydney)AP-Southeast (Sydney) NodeBalancersAP-Southeast (Sydney) BackupsAP-Southeast (Sydney) Linode Kubernetes EngineAP-Southeast (Sydney) Block StorageES-MAD (Madrid) Object StorageSE-STO (Stockholm)SE-STO (Stockholm) BackupsSE-STO (Stockholm) Block StorageSE-STO (Stockholm) NodeBalancersSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle)US-SEA (Seattle) BackupsUS-SEA (Seattle) Block StorageUS-SEA (Seattle) NodeBalancersUS-SEA (Seattle) Linode Kubernetes EngineIT-MIL (Milan)JP-OSA (Osaka) BackupsJP-OSA (Osaka) Block StorageJP-OSA (Osaka) NodeBalancersJP-OSA (Osaka) Linode Kubernetes EngineGB-LON (London 2)JP-OSA (Osaka)IN-MAA (Chennai) BackupsIN-MAA (Chennai) Block StorageIN-MAA (Chennai) NodeBalancersIN-MAA (Chennai) Linode Kubernetes EngineAU-MEL (Melbourne)IN-MAA (Chennai)ID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) BackupsBR-GRU (São Paulo) Block StorageBR-GRU (São Paulo) NodeBalancersNL-AMS (Amsterdam) Object StorageID-CGK (Jakarta)NL-AMS (Amsterdam) BackupsNL-AMS (Amsterdam) Block StorageNL-AMS (Amsterdam) NodeBalancersIT-MIL (Milan) Object StorageBR-GRU (São Paulo) Linode Kubernetes EngineBR-GRU (São Paulo)ES-MAD (Madrid) BackupsES-MAD (Madrid) Block StorageES-MAD (Madrid) NodeBalancersUS-MIA (Miami) Object StorageNL-AMS (Amsterdam) Linode Kubernetes EngineNL-AMS (Amsterdam)IT-MIL (Milan) BackupsIT-MIL (Milan) Block StorageIT-MIL (Milan) NodeBalancersUS-LAX (Los Angeles) Object StorageES-MAD (Madrid) Linode Kubernetes EngineUS-MIA (Miami)US-MIA (Miami) BackupsUS-MIA (Miami) Block StorageUS-MIA (Miami) NodeBalancersGB-LON (London 2) Object StorageIT-MIL (Milan) Linode Kubernetes EngineUS-LAX (Los Angeles)ID-CGK (Jakarta) BackupsID-CGK (Jakarta) Block StorageID-CGK (Jakarta) NodeBalancersAU-MEL (Melbourne) Object StorageUS-MIA (Miami) Linode Kubernetes EngineES-MAD (Madrid)US-LAX (Los Angeles) BackupsUS-LAX (Los Angeles) Block StorageUS-LAX (Los Angeles) NodeBalancersIN-BOM-2 (Mumbai 2) Object StorageUS-LAX (Los Angeles) Linode Kubernetes EngineAU-MEL (Melbourne)GB-LON (London 2) BackupsGB-LON (London 2) Block StorageGB-LON (London 2) NodeBalancersDE-FRA-2 (Frankfurt 2) Object StorageGB-LON (London 2) Linode Kubernetes EngineGB-LON (London 2)AU-MEL (Melbourne) BackupsAU-MEL (Melbourne) Block StorageAU-MEL (Melbourne) NodeBalancersSG-SIN-2 (Singapore 2) Object StorageAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2)IN-BOM-2 (Mumbai 2) BackupsIN-BOM-2 (Mumbai 2) Block StorageIN-BOM-2 (Mumbai 2) NodeBalancersJP-TYO-3 (Tokyo 3) Object StorageIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2)DE-FRA-2 (Frankfurt 2) BackupsDE-FRA-2 (Frankfurt 2) Block StorageDE-FRA-2 (Frankfurt 2) NodeBalancersDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2)SG-SIN-2 (Singapore 2) BackupsSG-SIN-2 (Singapore 2) Block StorageSG-SIN-2 (Singapore 2) NodeBalancersSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3)JP-TYO-3 (Tokyo) BackupsJP-TYO-3 (Tokyo 3) Block StorageJP-TYO-3 (Tokyo 3) NodeBalancersJP-TYO-3 (Tokyo 3) Linode Kubernetes EngineZA-JNB (Johannesburg)NZ-AKL (Auckland)CO-BOG (Bogota)US-DEN (Denver)DE-HAM (Hamburg)US-HOU (Houston)MY-KUL (Kuala Lumpur)FR-MRS (Marseille)MX-QRO (Queretaro)CL-SCL (Santiago)FR-PAR-2 (Paris 2)
Timeline · 3 updates

Read the full incident report →

Minor April 29, 2026

Object Storage Key creation and validation failing with error 403 in multiple data centers

Detected by Pingoru
Apr 29, 2026, 09:22 AM UTC
Resolved
Apr 29, 2026, 07:19 PM UTC
Duration
9h 57m
Affected: US-East (Newark) Object StorageUS-Southeast (Atlanta) Object StorageUS-IAD (Washington) Object StorageUS-ORD (Chicago) Object StorageEU-Central (Frankfurt) Object StorageAP-South (Singapore) Object StorageFR-PAR (Paris) Object StorageSE-STO (Stockholm) Object StorageUS-SEA (Seattle) Object StorageJP-OSA (Osaka) Object StorageIN-MAA (Chennai) Object StorageID-CGK (Jakarta) Object StorageBR-GRU (Sao Paulo) Object StorageES-MAD (Madrid) Object StorageGB-LON (London 2)AU-MEL (Melbourne)NL-AMS (Amsterdam) Object StorageIT-MIL (Milan) Object StorageUS-MIA (Miami) Object StorageUS-LAX (Los Angeles) Object StorageGB-LON (London 2) Object StorageAU-MEL (Melbourne) Object StorageIN-BOM-2 (Mumbai 2) Object StorageDE-FRA-2 (Frankfurt 2) Object StorageSG-SIN-2 (Singapore 2) Object StorageJP-TYO-3 (Tokyo 3) Object Storage
Timeline · 6 updates

Read the full incident report →

Minor April 24, 2026

Service Issue - Linode Kubernetes Engine (LKE)

Detected by Pingoru
Apr 24, 2026, 07:27 PM UTC
Resolved
Apr 28, 2026, 03:16 PM UTC
Duration
3d 19h
Affected: US-East (Newark) NodeBalancersUS-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) NodeBalancersUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) NodeBalancersUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) NodeBalancersUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) NodeBalancersUS-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago) NodeBalancersUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto) NodeBalancersCA-Central (Toronto) Linode Kubernetes EngineEU-West (London) NodeBalancersEU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt) NodeBalancersEU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris) NodeBalancersFR-PAR (Paris) Linode Kubernetes EngineAP-South (Singapore) NodeBalancersAP-South (Singapore) Linode Kubernetes EngineAP-Northeast-2 (Tokyo 2) NodeBalancersAP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai) NodeBalancersAP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney) NodeBalancersAP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm) NodeBalancersSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle) NodeBalancersUS-SEA (Seattle) Linode Kubernetes EngineJP-OSA (Osaka) NodeBalancersJP-OSA (Osaka) Linode Kubernetes EngineIN-MAA (Chennai) NodeBalancersIN-MAA (Chennai) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) NodeBalancersNL-AMS (Amsterdam) NodeBalancersBR-GRU (São Paulo) Linode Kubernetes EngineES-MAD (Madrid) NodeBalancersNL-AMS (Amsterdam) Linode Kubernetes EngineIT-MIL (Milan) NodeBalancersES-MAD (Madrid) Linode Kubernetes EngineUS-MIA (Miami) NodeBalancersIT-MIL (Milan) Linode Kubernetes EngineID-CGK (Jakarta) NodeBalancersUS-MIA (Miami) Linode Kubernetes EngineUS-LAX (Los Angeles) NodeBalancersUS-LAX (Los Angeles) Linode Kubernetes EngineGB-LON (London 2) NodeBalancersGB-LON (London 2) Linode Kubernetes EngineAU-MEL (Melbourne) NodeBalancersAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) NodeBalancersIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) NodeBalancersDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) NodeBalancersSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) NodeBalancersJP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Timeline · 9 updates

Read the full incident report →

Notice April 16, 2026

Linode Kubernetes Engine Standard and Enterprise provisioning failures in all regions

Detected by Pingoru
Apr 16, 2026, 01:20 PM UTC
Resolved
Apr 17, 2026, 01:30 PM UTC
Duration
1d
Affected: US-East (Newark) Linode Kubernetes EngineUS-Central (Dallas) Linode Kubernetes EngineUS-West (Fremont) Linode Kubernetes EngineUS-Southeast (Atlanta) Linode Kubernetes EngineUS-IAD (Washington) Linode Kubernetes EngineUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto) Linode Kubernetes EngineEU-West (London) Linode Kubernetes EngineEU-Central (Frankfurt) Linode Kubernetes EngineFR-PAR (Paris) Linode Kubernetes EngineAP-South (Singapore) Linode Kubernetes EngineAP-Northeast (Tokyo 2) Linode Kubernetes EngineAP-West (Mumbai) Linode Kubernetes EngineAP-Southeast (Sydney) Linode Kubernetes EngineSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineES-MAD (Madrid) Linode Kubernetes EngineIT-MIL (Milan) Linode Kubernetes EngineUS-MIA (Miami) Linode Kubernetes EngineUS-LAX (Los Angeles) Linode Kubernetes EngineGB-LON (London 2) Linode Kubernetes EngineAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) Linode Kubernetes Engine
Timeline · 9 updates

Read the full incident report →

Major April 7, 2026

Emerging Service Issue - Network - London 2(gb-lon)

Detected by Pingoru
Apr 07, 2026, 09:02 AM UTC
Resolved
Apr 08, 2026, 06:32 AM UTC
Duration
21h 30m
Affected: GB-LON (London 2)
Timeline · 3 updates
  1. investigating Apr 07, 2026, 09:02 AM UTC

    Our team is investigating an emerging service issue affecting connectivity to our Linode infrastructure in the London 2(gb-ion) region likely caused due to a upstream AS. We will continue to share more details as we verify this.

  2. monitoring Apr 07, 2026, 10:17 AM UTC

    We've determined that the impact of the issue caused by an upstream AS has been mitigated. We continue to monitor the situation until we recieve further confirmation of the resolution.

  3. resolved Apr 08, 2026, 06:32 AM UTC

    We haven’t observed any additional connectivity issues and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Read the full incident report →

Minor April 7, 2026

Emerging Service Issue - Object Storage - us-east-1

Detected by Pingoru
Apr 07, 2026, 12:50 AM UTC
Resolved
Apr 07, 2026, 01:39 AM UTC
Duration
48m
Affected: US-East (Newark) Object Storage
Timeline · 3 updates
  1. investigating Apr 07, 2026, 12:50 AM UTC

    Our team is investigating an emerging service issue affecting Object Storage in us-east-1. We will share additional updates as we have more information.

  2. identified Apr 07, 2026, 01:13 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Apr 07, 2026, 01:39 AM UTC

    This incident has been resolved.

Read the full incident report →