
Linode Status
Real-time updates of Linode issues and outages
Linode status is Operational
Linode Manager and API
US-Central (Dallas)
US-LAX (Los Angeles)
US-LAX (Los Angeles) Block Storage
Active Incidents
We are currently investigating an issue where 5xx errors are sometimes being triggered when attempting to connect to api.linode.com and cloud.linode.com. As our teams investigate, please open a Support ticket from the Cloud Manager to speak with our Support team.
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.
Recently Resolved Incidents
Our team is investigating an emerging service issue affecting services US-LAX (Los Angeles). We will share additional updates as we have more information.
We became aware of a network performance degradation issue in Dallas, caused by outbound routing problems affecting a small subset of users. The issue occurred between approximately 19:58 UTC and 21:30 UTC on June 17, 2025. Based on current observations, service has returned to normal. Additional details are available on the Akamai Community. We will continue monitoring to ensure the issue has been fully resolved.
If you are still experiencing issues, please open a Support ticket for assistance.
We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
Linode Outage Survival Guide
Linode Components
Linode.com
Linode Manager and API
We are currently investigating an issue where 5xx errors are sometimes being triggered when attempting to connect to api.linode.com and cloud.linode.com. As our teams investigate, please open a Support ticket from the Cloud Manager to speak with our Support team.
Linode Hosted DNS Service
Linode Longview
Linode Managed Databases
Linode Metadata Service
Linode Regions
US-East (Newark)
US-Central (Dallas)
We became aware of a network performance degradation issue in Dallas, caused by outbound routing problems affecting a small subset of users. The issue occurred between approximately 19:58 UTC and 21:30 UTC on June 17, 2025. Based on current observations, service has returned to normal. Additional details are available on the Akamai Community. We will continue monitoring to ensure the issue has been fully resolved.
If you are still experiencing issues, please open a Support ticket for assistance.
We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.
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)
AP-Northeast-2 (Tokyo 2)
AP-West (Mumbai)
AP-Southeast (Sydney)
SE-STO (Stockholm)
US-SEA (Seattle)
IT-MIL (Milan)
JP-OSA (Osaka)
IN-MAA (Chennai)
ID-CGK (Jakarta)
BR-GRU (São 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)
SG-SIN-2 (Singapore 2)
DE-FRA-2 (Frankfurt 2)
JP-TYO-3 (Tokyo 3)
ZA-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)
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
BR-GRU (São Paulo) Backups
NL-AMS (Amsterdam) Backups
ES-MAD (Madrid) Backups
IT-MIL (Milan) Backups
US-MIA (Miami) Backups
ID-CGK (Jakarta) Backups
US-LAX (Los Angeles) Backups
GB-LON (London 2) Backups
AU-MEL (Melbourne) Backups
IN-BOM-2 (Mumbai 2) Backups
DE-FRA-2 (Frankfurt 2) Backups
SG-SIN-2 (Singapore 2) Backups
JP-TYO-3 (Tokyo) 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
BR-GRU (São Paulo) Block Storage
NL-AMS (Amsterdam) Block Storage
ES-MAD (Madrid) Block Storage
IT-MIL (Milan) Block Storage
US-MIA (Miami) Block Storage
ID-CGK (Jakarta) Block Storage
US-LAX (Los Angeles) Block Storage
Our team is investigating an emerging service issue affecting services US-LAX (Los Angeles). We will share additional updates as we have more information.