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

Linode Status

← Current Status
Emerging Service Issue - GPU and VPU Booting issues
Update - 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.
Dec 17, 2025 - 13:40 UTC
Update - 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.
Dec 04, 2025 - 20:51 UTC
Identified - 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.
Dec 03, 2025 - 16:48 UTC
Investigating - Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.
Dec 03, 2025 - 15:15 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 (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
Dec 18, 2025
Service Issue - Cloud Manager, Linode DB and API
Resolved - We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Dec 18, 22:32 UTC
Update - We are continuing to monitor 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.
Dec 3, 22:56 UTC
Monitoring - At this time we have been able to correct the issue affecting the Cloud Manager and API. We will be monitoring this 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.
Nov 22, 15:14 UTC
Update - We are continuing to investigate this issue.
Nov 22, 14:07 UTC
Update - Our team is continuing to investigate the root cause of a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. We applied mitigation steps and systems began recovering at approximately 13:35 UTC on Saturday November 22, 2025. We will share additional updates as we have more information.
Nov 22, 14:02 UTC
Update - We are continuing to investigate this issue. We will share additional updates as we have more information.
Nov 22, 12:25 UTC
Investigating - Our team is investigating an emerging service issue affecting Cloud Manager and API in all regions. We will share additional updates as we have more information.
Nov 22, 11:37 UTC
Dec 17, 2025

Unresolved incident: Emerging Service Issue - GPU and VPU Booting issues.

Dec 16, 2025
Emergency Network Maintenance - JP-OSA (Osaka, JP)
Completed - The scheduled maintenance has been completed.
Dec 16, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 16, 14:00 UTC
Scheduled - We will be performing emergency network maintenance in our JP-OSA (Osaka, JP) Data Center beginning on December 16th, 14:00 UTC until December 16th 16:00 UTC. Customers in this region may experience brief connectivity disruptions during this window.
Dec 12, 16:44 UTC
Service Issue - US-Southeast (Atlanta)
Postmortem - Read details
Dec 16, 06:25 UTC
Resolved - We haven’t observed any additional issues, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Dec 16, 05:17 UTC
Monitoring - At this time, we have been able to correct the issues affecting connectivity in our US-Southeast (Atlanta) 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.
Dec 16, 04:31 UTC
Update - Our team has identified the issue in the US-Southeast (Atlanta) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Dec 16, 03:08 UTC
Update - We are continuing to investigate this issue. We will share additional updates as we have more information.
Dec 16, 02:42 UTC
Investigating - Our team is investigating an issue in the US-Southeast (Atlanta) data center. During this time, users may experience interruption of service or will be unable to access their Linodes. The impact is limited to some hosts in this data center. We will share additional updates as we have more information.
Dec 16, 01:44 UTC
Dec 15, 2025

No incidents reported.

Dec 14, 2025

No incidents reported.

Dec 13, 2025

No incidents reported.

Dec 12, 2025

No incidents reported.

Dec 11, 2025
"Monitor->Alerts(BETA)" Service Maintenance
Completed - The scheduled maintenance has been completed.
Dec 11, 12:30 UTC
Verifying - Verification is currently underway for the maintenance items.
Dec 11, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 11, 08:00 UTC
Scheduled - On Thursday, December 11th, at approximately 08:00 AM UTC, we will be performing the maintenance of "Monitor->Alerts(BETA)" service.

During this maintenance window, the Monitor->Alerts(BETA) Service remains active and you will continue to receive notifications as usual, though occasional duplicates may occur. Please note that you will be unable to create, edit, or delete alert rules until the maintenance is complete.
Dec 8, 17:31 UTC
Dec 10, 2025
Connectivity Issue - US-IAD (Washington)
Resolved - We haven't observed any additional connectivity issues in our US-IAD (Washington) data center and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Dec 10, 02:41 UTC
Update - We are continuing to investigate this issue.
Dec 9, 22:43 UTC
Update - We are continuing to investigate connectivity issues in the US-IAD (Washington) data center. Users may experience intermittent timeouts and errors for services hosted there. We will provide updates as more information becomes available.
Dec 9, 19:09 UTC
Update - We continue to investigate the issue and shall provide an update as we progress.
Dec 9, 17:14 UTC
Investigating - Our team is investigating an issue affecting connectivity in our US-IAD (Washington) 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.
Dec 9, 16:25 UTC
Dec 9, 2025
Service Issue - Compute Hosts - Multiple Regions
Postmortem - Read details
Dec 12, 15:39 UTC
Resolved - We haven't observed any additional issues with jobs being issued and completed on Compute hosts, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Dec 9, 16:59 UTC
Monitoring - At this time we have been able to correct the issue affecting jobs being issued and completed on Compute hosts. We will be monitoring this 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.
Dec 8, 21:17 UTC
Identified - Our team has identified the issue affecting jobs being issued and completed on compute hosts. We are working quickly to implement a fix to these hosts, and we will provide an update as soon as the solution is in place.

If you continue experiencing issues or need further assistance, please open a Support ticket from the Linode Manager.
Dec 8, 17:13 UTC
Investigating - Our team is investigating an emerging service issue affecting completing jobs issued to compute hosts in multiple regions. We will share additional updates as we have more information.
Dec 8, 16:38 UTC
Network Maintenance - US-IAD (Washington, DC)
Completed - The scheduled maintenance has been completed.
Dec 9, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 9, 05:00 UTC
Scheduled - On Tuesday, December 9th, at approximately 05:00 AM UTC, we will be performing maintenance on the border routers in the US-IAD region to complete an upgrade. This upgrade will help reduce bottlenecks and allow for greater capacity across the region.

Due to the redundant nature of these systems, we do not expect downtime during this maintenance. While not expected, customers may experience brief periods of packet loss or latency during the maintenance window. The duration of this maintenance may last up to 6 hours.
Nov 19, 18:09 UTC
Dec 8, 2025
Scheduled Maintenance for Linode Cloud Manager, API and BlockStorage
Completed - The scheduled maintenance has been completed.
Dec 8, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 8, 06:00 UTC
Scheduled - Scheduled Maintenance for Linode Cloud Manager, API and BlockStorage will be implemented during the 3 hour window beginning at 2025-12-08 06:00 UTC
Dec 7, 18:21 UTC
Dec 7, 2025

No incidents reported.

Dec 6, 2025

No incidents reported.

Dec 5, 2025
Emerging Service Issue - Object Storage - it-mil (Milan)
Resolved - After further investigation it was determined that this issue is not causing any customer impact or service disruption, we apologize for the confusion.
Dec 5, 22:55 UTC
Investigating - Our team is investigating an emerging service issue affecting Object Storage in it-mil (Milan, Italy). We will share additional updates as we have more information.
Dec 5, 17:48 UTC
Service Issue - Managed Databases
Postmortem - Read details
Dec 18, 18:16 UTC
Resolved - We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Dec 5, 00:40 UTC
Update - There was a recurrence from 19:28 UTC to 19:42 UTC because our third party experienced issues again while working on their end. We can confirm the issue is no longer happening at this moment. We are continuing to monitor for any further issues.
Dec 4, 20:14 UTC
Monitoring - At this time we have been able to confirm the issue affecting the Cloud Manager and API was related to a vendor having issues on their side, these issues have been fixed on their end and our services are back on line as of 18:55 UTC. We will be monitoring this 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.
Dec 4, 19:12 UTC
Update - We are continuing to investigate this issue.
Dec 4, 18:50 UTC
Investigating - Our team is investigating a service issue affecting the Managed Databases service. During this time, users may experience issues when attempting to configure, update, provision, and view Managed Databases via the Cloud Manager or Linode API. Existing Managed Database cluster operations are not affected.

We will share additional updates as we have more information.
Dec 4, 17:43 UTC
Dec 4, 2025
Scheduled Maintenance for Linode Manager and API in Chicago (ORD) Data Center
Completed - The scheduled maintenance has been completed.
Dec 4, 09:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 4, 06:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Dec 3, 21:36 UTC
Scheduled - The Linode API will be undergoing scheduled maintenance during this time. We will be monitoring this to ensure that the service is stable. If you experience issues, open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
Dec 3, 15:32 UTC
← Incident History Powered by Atlassian Statuspage