Linode Status
Real-time updates of Linode issues and outages
Linode status is Partially Degraded Service
AP-South (Singapore)
AP-Northeast-2 (Tokyo 2)
AP-West (Mumbai)
JP-OSA (Osaka)
IN-MAA (Chennai)
ID-CGK (Jakarta)
US-LAX (Los Angeles)
Active Incidents
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an issue affecting the Object Storage service in our LAX location. During this time, users may experience connection timeouts and errors with this service.
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
Recently Resolved Incidents
Our team is investigating an emerging service issue affecting Object Storage in SEA. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
Linode Outage Survival Guide
Linode Components
Linode.com
Linode Manager and API
Linode Hosted DNS Service
Linode Longview
Linode Managed Databases
Linode Regions
US-East (Newark)
US-Central (Dallas)
US-West (Fremont)
US-Southeast (Atlanta)
US-IAD (Washington)
US-ORD (Chicago)
CA-Central (Toronto)
EU-West (London)
EU-Central (Frankfurt)
FR-PAR (Paris)
AP-South (Singapore)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
AP-Northeast-2 (Tokyo 2)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
AP-West (Mumbai)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
AP-Southeast (Sydney)
SE-STO (Stockholm)
US-SEA (Seattle)
IT-MIL (Milan)
JP-OSA (Osaka)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
IN-MAA (Chennai)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
ID-CGK (Jakarta)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
BR-GRU (Sao Paulo)
NL-AMS (Amsterdam)
US-MIA (Miami)
US-LAX (Los Angeles)
Our team is investigating an issue affecting the Object Storage service in our LAX location. During this time, users may experience connection timeouts and errors with this service.
ES-MAD (Madrid)
AU-MEL (Melbourne)
GB-LON (London 2)
IN-BOM-2 (Mumbai 2)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
SG-SIN-2 (Singapore 2)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
DE-FRA-2 (Frankfurt 2)
JP-TYO-3 (Tokyo 3)
Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. If you are still experiencing issues and unable to open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to [email protected].
ZA-JNB (Johannesburg)
Linode Backups
US-East (Newark) Backups
US-Central (Dallas) Backups
US-West (Fremont) Backups
US-Southeast (Atlanta) Backups
US-IAD (Washington) Backups
US-ORD (Chicago) Backups
CA-Central (Toronto) Backups
EU-West (London) Backups
EU-Central (Frankfurt) Backups
FR-PAR (Paris) Backups
AP-South (Singapore) Backups
AP-Northeast-2 (Tokyo 2) Backups
AP-West (Mumbai) Backups
AP-Southeast (Sydney) Backups
SE-STO (Stockholm) Backups
US-SEA (Seattle) Backups
JP-OSA (Osaka) Backups
IN-MAA (Chennai) Backups
Linode Block Storage
US-East (Newark) Block Storage
US-Central (Dallas) Block Storage
US-West (Fremont) Block Storage
US-Southeast (Atlanta) Block Storage
US-IAD (Washington) Block Storage
US-ORD (Chicago) Block Storage
CA-Central (Toronto) Block Storage
EU-West (London) Block Storage
EU-Central (Frankfurt) Block Storage
FR-PAR (Paris) Block Storage
AP-South (Singapore) Block Storage
AP-Northeast-2 (Tokyo 2) Block Storage
AP-West (Mumbai) Block Storage
AP-Southeast (Sydney) Block Storage
SE-STO (Stockholm) Block Storage
US-SEA (Seattle) Block Storage
JP-OSA (Osaka) Block Storage
IN-MAA (Chennai) Block Storage
Linode NodeBalancers
US-East (Newark) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
US-Central (Dallas) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
US-West (Fremont) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
US-Southeast (Atlanta) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
US-IAD (Washington) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
US-ORD (Chicago) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
CA-Central (Toronto) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
EU-West (London) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
EU-Central (Frankfurt) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
FR-PAR (Paris) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
AP-South (Singapore) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
AP-Northeast-2 (Tokyo 2) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
AP-West (Mumbai) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
AP-Southeast (Sydney) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
SE-STO (Stockholm) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
US-SEA (Seattle) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
JP-OSA (Osaka) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
IN-MAA (Chennai) NodeBalancers
Our team is investigating an emerging service issue affecting Node Balancers in all regions. We will share additional updates as we have more information.
Linode Object Storage
US-East (Newark) Object Storage
US-Southeast (Atlanta) Object Storage
US-IAD (Washington) Object Storage
US-ORD (Chicago) Object Storage
EU-Central (Frankfurt) Object Storage
AP-South (Singapore) Object Storage
FR-PAR (Paris) Object Storage
SE-STO (Stockholm) Object Storage
US-SEA (Seattle) Object Storage
Our team is investigating an emerging service issue affecting Object Storage in SEA. We will share additional updates as we have more information.
JP-OSA (Osaka) Object Storage
IN-MAA (Chennai) Object Storage
ID-CGK (Jakarta) Object Storage
BR-GRU (Sao Paulo) Object Storage
ES-MAD (Madrid) Object Storage
AP-West (Mumbai)
EU-West (London)
GB-LON (London 2)
AU-MEL (Melbourne)
Linode Kubernetes Engine
US-East (Newark) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
US-Central (Dallas) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
US-West (Fremont) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
US-Southeast (Atlanta) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
US-IAD (Washington) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
US-ORD (Chicago) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
CA-Central (Toronto) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
EU-West (London) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
EU-Central (Frankfurt) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
FR-PAR (Paris) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
AP-South (Singapore) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
AP-West (Mumbai) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
AP-Southeast (Sydney) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
SE-STO (Stockholm) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
US-SEA (Seattle) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
JP-OSA (Osaka) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
IN-MAA (Chennai) Linode Kubernetes Engine
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
ID-CGK (Jakarta)
Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). During this time users may have difficulty connecting to their cluster control plane. Internal cluster services are not impacted at this time. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
