View all products
Compute
Storage
Networking
Databases
Services
Solutions
Pricing
Library
Technical Resources
Community
Marketplace
What's New

Linode Status

← Current Status
5xx Errors on api.linode.com and cloud.linode.com
Update - At this time we have been able to identify the cause of the issue affecting the Cloud Manager and API. We will continue monitoring to ensure that the service remains stable. 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 support@linode.com.
Jun 21, 2025 - 04:21 UTC
Monitoring - The issue impacting api.linode.com and cloud.linode.com has subsided by 00:40 UTC, June 21, 2025, and there has been no recurrence since. We are actively monitoring this to ensure that the service remains stable while investigating the root cause. 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 support@linode.com.
Jun 21, 2025 - 03:15 UTC
Update - The issue with sporadic 5xx errors when accessing api.linode.com and cloud.linode.com appears to have remained stable for the past hour. Investigations into the root cause and monitoring for recurrences are ongoing. If you are encountering any issues with your services which you believe may be related to this situation, please open a Support ticket from the Cloud Manager to speak with our Support team.
Jun 21, 2025 - 02:10 UTC
Investigating - 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.
Jun 21, 2025 - 00:48 UTC
Linode.com Operational
Linode Manager and API Operational
Hosted DNS Service Operational
Longview Operational
Managed Databases Operational
Regions Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
US-IAD (Washington) Operational
US-ORD (Chicago) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
FR-PAR (Paris) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
SE-STO (Stockholm) Operational
US-SEA (Seattle) Operational
IT-MIL (Milan) Operational
JP-OSA (Osaka) Operational
IN-MAA (Chennai) Operational
ID-CGK (Jakarta) Operational
BR-GRU (São Paulo) Operational
NL-AMS (Amsterdam) Operational
US-MIA (Miami) Operational
US-LAX (Los Angeles) Operational
ES-MAD (Madrid) Operational
AU-MEL (Melbourne) Operational
GB-LON (London 2) Operational
IN-BOM-2 (Mumbai 2) Operational
SG-SIN-2 (Singapore 2) Operational
DE-FRA-2 (Frankfurt 2) Operational
JP-TYO-3 (Tokyo 3) Operational
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
Backups Operational
US-East (Newark) Backups Operational
US-Central (Dallas) Backups Operational
US-West (Fremont) Backups Operational
US-Southeast (Atlanta) Backups Operational
US-IAD (Washington) Backups Operational
US-ORD (Chicago) Backups Operational
CA-Central (Toronto) Backups Operational
EU-West (London) Backups Operational
EU-Central (Frankfurt) Backups Operational
FR-PAR (Paris) Backups Operational
AP-South (Singapore) Backups Operational
AP-Northeast-2 (Tokyo 2) Backups Operational
AP-West (Mumbai) Backups Operational
AP-Southeast (Sydney) Backups Operational
SE-STO (Stockholm) Backups Operational
US-SEA (Seattle) Backups Operational
JP-OSA (Osaka) Backups Operational
IN-MAA (Chennai) Backups Operational
BR-GRU (São Paulo) Backups Operational
NL-AMS (Amsterdam) Backups Operational
ES-MAD (Madrid) Backups Operational
IT-MIL (Milan) Backups Operational
US-MIA (Miami) Backups Operational
ID-CGK (Jakarta) Backups Operational
US-LAX (Los Angeles) Backups Operational
GB-LON (London 2) Backups Operational
AU-MEL (Melbourne) Backups Operational
IN-BOM-2 (Mumbai 2) Backups Operational
DE-FRA-2 (Frankfurt 2) Backups Operational
SG-SIN-2 (Singapore 2) Backups Operational
JP-TYO-3 (Tokyo) Backups Operational
Block Storage Operational
US-East (Newark) Block Storage Operational
US-Central (Dallas) Block Storage Operational
US-West (Fremont) Block Storage Operational
US-Southeast (Atlanta) Block Storage Operational
US-IAD (Washington) Block Storage Operational
US-ORD (Chicago) Block Storage Operational
CA-Central (Toronto) Block Storage Operational
EU-West (London) Block Storage Operational
EU-Central (Frankfurt) Block Storage Operational
FR-PAR (Paris) Block Storage Operational
AP-South (Singapore) Block Storage Operational
AP-Northeast-2 (Tokyo 2) Block Storage Operational
AP-West (Mumbai) Block Storage Operational
AP-Southeast (Sydney) Block Storage Operational
SE-STO (Stockholm) Block Storage Operational
US-SEA (Seattle) Block Storage Operational
JP-OSA (Osaka) Block Storage Operational
IN-MAA (Chennai) Block Storage Operational
BR-GRU (São Paulo) Block Storage Operational
NL-AMS (Amsterdam) Block Storage Operational
ES-MAD (Madrid) Block Storage Operational
IT-MIL (Milan) Block Storage Operational
US-MIA (Miami) Block Storage Operational
ID-CGK (Jakarta) Block Storage Operational
US-LAX (Los Angeles) Block Storage Operational
GB-LON (London 2) Block Storage Operational
AU-MEL (Melbourne) Block Storage Operational
IN-BOM-2 (Mumbai 2) Block Storage Operational
DE-FRA-2 (Frankfurt 2) Block Storage Operational
SG-SIN-2 (Singapore 2) Block Storage Operational
JP-TYO-3 (Tokyo 3) Block Storage Operational
NodeBalancers Operational
US-East (Newark) NodeBalancers Operational
US-Central (Dallas) NodeBalancers Operational
US-West (Fremont) NodeBalancers Operational
US-Southeast (Atlanta) NodeBalancers Operational
US-IAD (Washington) NodeBalancers Operational
US-ORD (Chicago) NodeBalancers Operational
CA-Central (Toronto) NodeBalancers Operational
EU-West (London) NodeBalancers Operational
EU-Central (Frankfurt) NodeBalancers Operational
FR-PAR (Paris) NodeBalancers Operational
AP-South (Singapore) NodeBalancers Operational
AP-Northeast-2 (Tokyo 2) NodeBalancers Operational
AP-West (Mumbai) NodeBalancers Operational
AP-Southeast (Sydney) NodeBalancers Operational
SE-STO (Stockholm) NodeBalancers Operational
US-SEA (Seattle) NodeBalancers Operational
JP-OSA (Osaka) NodeBalancers Operational
IN-MAA (Chennai) NodeBalancers Operational
BR-GRU (São Paulo) NodeBalancers Operational
NL-AMS (Amsterdam) NodeBalancers Operational
ES-MAD (Madrid) NodeBalancers Operational
IT-MIL (Milan) NodeBalancers Operational
US-MIA (Miami) NodeBalancers Operational
ID-CGK (Jakarta) NodeBalancers Operational
US-LAX (Los Angeles) NodeBalancers Operational
GB-LON (London 2) NodeBalancers Operational
AU-MEL (Melbourne) NodeBalancers Operational
IN-BOM-2 (Mumbai 2) NodeBalancers Operational
DE-FRA-2 (Frankfurt 2) NodeBalancers Operational
SG-SIN-2 (Singapore 2) NodeBalancers Operational
JP-TYO-3 (Tokyo 3) NodeBalancers Operational
Object Storage Operational
US-East (Newark) Object Storage Operational
US-Southeast (Atlanta) Object Storage Operational
US-IAD (Washington) Object Storage Operational
US-ORD (Chicago) Object Storage Operational
EU-Central (Frankfurt) Object Storage Operational
AP-South (Singapore) Object Storage Operational
FR-PAR (Paris) Object Storage Operational
SE-STO (Stockholm) Object Storage Operational
US-SEA (Seattle) Object Storage Operational
JP-OSA (Osaka) Object Storage Operational
IN-MAA (Chennai) Object Storage Operational
ID-CGK (Jakarta) Object Storage Operational
BR-GRU (Sao Paulo) Object Storage Operational
ES-MAD (Madrid) Object Storage Operational
GB-LON (London 2) Operational
AU-MEL (Melbourne) Operational
NL-AMS (Amsterdam) Object Storage Operational
IT-MIL (Milan) Object Storage Operational
US-MIA (Miami) Object Storage Operational
US-LAX (Los Angeles) Object Storage Operational
GB-LON (London 2) Object Storage Operational
AU-MEL (Melbourne) Object Storage Operational
IN-BOM-2 (Mumbai 2) Object Storage Operational
DE-FRA-2 (Frankfurt 2) Object Storage Operational
SG-SIN-2 (Singapore 2) Object Storage Operational
JP-TYO-3 (Tokyo 3) Object Storage Operational
Linode Kubernetes Engine Operational
US-East (Newark) Linode Kubernetes Engine Operational
US-Central (Dallas) Linode Kubernetes Engine Operational
US-West (Fremont) Linode Kubernetes Engine Operational
US-Southeast (Atlanta) Linode Kubernetes Engine Operational
US-IAD (Washington) Linode Kubernetes Engine Operational
US-ORD (Chicago) Linode Kubernetes Engine Operational
CA-Central (Toronto) Linode Kubernetes Engine Operational
EU-West (London) Linode Kubernetes Engine Operational
EU-Central (Frankfurt) Linode Kubernetes Engine Operational
FR-PAR (Paris) Linode Kubernetes Engine Operational
AP-South (Singapore) Linode Kubernetes Engine Operational
AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine Operational
AP-West (Mumbai) Linode Kubernetes Engine Operational
AP-Southeast (Sydney) Linode Kubernetes Engine Operational
SE-STO (Stockholm) Linode Kubernetes Engine Operational
US-SEA (Seattle) Linode Kubernetes Engine Operational
JP-OSA (Osaka) Linode Kubernetes Engine Operational
IN-MAA (Chennai) Linode Kubernetes Engine Operational
ID-CGK (Jakarta) Linode Kubernetes Engine Operational
BR-GRU (São Paulo) Linode Kubernetes Engine Operational
NL-AMS (Amsterdam) Linode Kubernetes Engine Operational
ES-MAD (Madrid) Linode Kubernetes Engine Operational
IT-MIL (Milan) Linode Kubernetes Engine Operational
US-MIA (Miami) Linode Kubernetes Engine Operational
US-LAX (Los Angeles) Linode Kubernetes Engine Operational
GB-LON (London 2) Linode Kubernetes Engine Operational
AU-MEL (Melbourne) Linode Kubernetes Engine Operational
IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine Operational
DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine Operational
SG-SIN-2 (Singapore 2) Linode Kubernetes Engine Operational
JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine Operational
Metadata Service Operational
US-East (Newark) Operational
US-Central (Dallas) Operational
US-West (Fremont) Operational
US-Southeast (Atlanta) Operational
US-IAD (Washington) Operational
US-ORD (Chicago) Operational
CA-Central (Toronto) Operational
EU-West (London) Operational
EU-Central (Frankfurt) Operational
FR-PAR (Paris) Operational
AP-South (Singapore) Operational
AP-Northeast-2 (Tokyo 2) Operational
AP-West (Mumbai) Operational
AP-Southeast (Sydney) Operational
SE-STO (Stockholm) Operational
US-SEA (Seattle) Operational
IT-MIL (Milan) Operational
JP-OSA (Osaka) Operational
IN-MAA (Chennai) Operational
ID-CGK (Jakarta) Operational
BR-GRU (São Paulo) Operational
NL-AMS (Amsterdam) Operational
US-MIA (Miami) Operational
US-LAX (Los Angeles) Operational
ES-MAD (Madrid) Operational
AU-MEL (Melbourne) Operational
GB-LON (London 2) Operational
IN-BOM-2 (Mumbai 2) Operational
SG-SIN-2 (Singapore 2) Operational
DE-FRA-2 (Frankfurt 2) Operational
JP-TYO-3 (Tokyo 3) Operational
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jun 22, 2025

No incidents reported today.

Jun 21, 2025

Unresolved incident: 5xx Errors on api.linode.com and cloud.linode.com.

Jun 20, 2025
Service Issue - US-LAX (Los Angeles)
Resolved - We haven’t observed any additional issues with the Block Storage service in US-LAX (Los Angeles), and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jun 20, 16:23 UTC
Monitoring - The issue has been identified and a fix has been implemented. We are currently monitoring the situation to ensure stability and will continue to watch for any further issues. Thank you for your patience.
Jun 20, 14:59 UTC
Update - We’re actively investigating this issue and will share additional updates as they become available. We sincerely apologize for any impact this may have and truly appreciate your patience as we work to resolve it.
Jun 20, 14:37 UTC
Update - Our team is investigating a service issue affecting Block Storage in US-LAX (Los Angeles). We are still working to identify the cause, and we will provide an update as soon as we have more information.
Jun 20, 13:45 UTC
Investigating - Our team is investigating an emerging service issue affecting services US-LAX (Los Angeles). We will share additional updates as we have more information.
Jun 20, 12:38 UTC
Linode Cloud Manager Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
Jun 20, 15:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 20, 13:00 UTC
Scheduled - The Linode Cloud Manager will undergo scheduled failover testing between 13:00 UTC and 15:00 UTC on June 20, 2025. During this window, the cloud manager service should not be disrupted. We will update this status page if we encounter any unexpected issues.
Jun 16, 18:18 UTC
Jun 19, 2025

No incidents reported.

Jun 18, 2025
Network performance degradation issues in Dallas
Resolved - We haven’t observed any additional connectivity issues in our US-Central (Dallas) data center, and will now consider this incident resolved.

If you continue to experience problems, please open a Support ticket for assistance.
Jun 18, 03:18 UTC
Monitoring - 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.
Jun 18, 00:37 UTC
Jun 17, 2025
Scheduled Network Maintenance - JP-TYO-3 (Tokyo 3)
Completed - The scheduled maintenance has been completed.
Jun 17, 14:24 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 17, 13:00 UTC
Scheduled - We will be performing network maintenance in our JP-TYO-3 (Tokyo 3) data center from 13:00 UTC to 17:00 UTC on June 17, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
May 22, 15:31 UTC
Scheduled Emergency Network Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Jun 17, 06:02 UTC
Verifying - Verification is currently underway for the maintenance items.
Jun 17, 05:59 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 17, 05:00 UTC
Scheduled - We will be performing an emergency network maintenance in our US-Central (Dallas) data center from 05:00 (UTC) until 09:00 (UTC) on Tuesday, June 17th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Jun 14, 17:17 UTC
Jun 16, 2025
Scheduled Emergency Network Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Jun 16, 07:49 UTC
Verifying - Verification is currently underway for the maintenance items.
Jun 16, 07:39 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 16, 05:00 UTC
Scheduled - We will be performing an emergency network maintenance in our US-Central (Dallas) data center from 05:00 (UTC) until 09:00 (UTC) on Monday, June 16th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Jun 14, 17:15 UTC
Jun 15, 2025

No incidents reported.

Jun 14, 2025

No incidents reported.

Jun 13, 2025
DBaaS - Degraded provisioning
Resolved - This incident has been resolved.
Jun 13, 03:55 UTC
Investigating - Provisioning is degraded due to ongoing issue. Services are recovering. We are still monitoring.
Jun 12, 20:04 UTC
Jun 12, 2025
Jun 11, 2025

No incidents reported.

Jun 10, 2025

No incidents reported.

Jun 9, 2025

No incidents reported.

Jun 8, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage