View All Products
Compute
Storage
Networking
Databases
Services
Developer Tools
Industries
Pricing
Community
Engage With Us

Linode Status

← Current Status
Service Issue - Block Storage (Toronto, Frankfurt, Newark, Sydney, and Fremont)
Update - Our team identified an additional impact to Block Storage in the US-West (Fremont) data center with an initial, brief period of impact around 14:43 UTC and another period of impact between approximately 15:40 and 15:58 UTC on December 10, 2024. During this time, users may have experienced connection timeouts and errors with this service. This impact was introduced by maintenance being performed across clusters to prevent this impact going forward. We have been able to resolve the issue and continue to monitor to ensure that the service remains stable.
Dec 11, 2024 - 16:16 UTC
Monitoring - 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.
Dec 09, 2024 - 08:47 UTC
Investigating - Our team identified an issue affecting the Block Storage service in Sydney, Australia, data center, on December 9, 2024, at 7:25 UTC. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Dec 09, 2024 - 08:33 UTC
Update - Our team identified an issue affecting the Block Storage service in Sydney, Australia, data center, on December 9, 2024, at 7:25 UTC. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Dec 09, 2024 - 08:30 UTC
Update - We have identified a recurrence of the issue.
Dec 09, 2024 - 08:24 UTC
Update - Our team identified an issue affecting the Block Storage service in our Newark, New Jersey, data center, on December 5, 2024, between 06:40 and 07:49 UTC. At this time we have been able to correct the issues affecting the 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.
Dec 05, 2024 - 09:37 UTC
Monitoring - 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.
Dec 03, 2024 - 11:52 UTC
Investigating - Our team is investigating a recurrence of the issue affecting the Block Storage service in our Toronto and Frankfurt data centers. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Dec 03, 2024 - 11:32 UTC
Monitoring - 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.
Dec 03, 2024 - 10:46 UTC
Update - Our team is investigating an issue affecting the Block Storage service in our Toronto and Frankfurt data centers. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Dec 03, 2024 - 09:52 UTC
Investigating - Our team is investigating an issue affecting the Block Storage service in our Toronto data center. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Dec 03, 2024 - 09:41 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 (Sao 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
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
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
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
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) Operational
BR-GRU (Sao Paulo) 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) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Emergency Network Maintenance - EU-Central (Frankfurt) Dec 12, 2024 21:00 - Dec 13, 2024 01:00 UTC
We will be performing an emergency network maintenance in our EU-Central (Frankfurt) data center beginning 12 December 2024 21:00 (UTC) until 13 December 2024 01:00 (UTC). During this time, users with resources in the EU-Central (Frankfurt) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region.
Posted on Dec 11, 2024 - 18:40 UTC
Past Incidents
Dec 12, 2024

No incidents reported today.

Dec 11, 2024
Emergency Maintenance for Linode Kubernetes Engine (LKE)
Completed - The scheduled maintenance has been completed.
Dec 11, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 11, 06:00 UTC
Scheduled - The LKE team will be performing emergency maintenance on Wednesday December 11th, 2024 from 09:00 UTC to 20:00 UTC. During this window, both the Container Storage Interface (CSI) and the Container Network Interface (CNI) are being restarted. You may experience a brief CNI or CSI interruption while these pods restart. We recommend pausing administrative activities during this time. If you encounter any persistent issues, please contact our support team for assistance.
Dec 6, 20:04 UTC
Dec 10, 2024
Service Issue - Custom Image Deployment Failures
Resolved - We haven't observed any additional issues with custom images, 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, 18:34 UTC
Monitoring - At this time we have been able to correct the issue causing Linode deployments to fail when using custom images. 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 5, 17:56 UTC
Identified - Our team has identified the issue causing Linode deployments to fail when using custom images that were uploaded on or after 13 November. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Dec 2, 16:05 UTC
Investigating - Our team is investigating an issue causing Linode deployments to fail when using custom images that were uploaded on or after 13 November. During this time, some users may be unable to deploy Linodes using custom images. We will share additional updates as we have more information.
Nov 27, 20:46 UTC
Service Issue - Block Storage - IN-MAA (Chennai)
Resolved - We haven’t observed any additional issues with the Block Storage service in Chennai data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Dec 10, 16:55 UTC
Monitoring - At this time we have been able to correct the issues affecting the Block Storage service in Chennai. Based on current observations, the service has resumed normal operations. We will be monitoring this to ensure that it remains stable while continuing to investigate the root cause. Please be aware that some customers may experience minor performance degradation during this period. If you continue to experience problems, please open a Support ticket for assistance.
Dec 10, 11:07 UTC
Identified - Our team has identified the issue affecting the Block Storage service in our Chennai 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 10, 10:22 UTC
Update - Our investigation narrowed down the impact to an issue affecting the Block Storage service in our Chennai data center. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Dec 10, 09:47 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Chennai 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 10, 09:10 UTC
Emergency Maintenance for Linode Kubernetes Engine (LKE) - US-ORD (Chicago)
Completed - The scheduled maintenance has been completed.
Dec 10, 12:57 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 10, 09:00 UTC
Scheduled - The LKE team will be performing emergency maintenance on Tuesday December 10th, 2024 from 09:00 UTC to 13:00 UTC. During this window, both the Container Storage Interface (CSI) and the Container Network Interface (CNI) are being restarted. You may experience a brief CNI or CSI interruption while these pods restart. We recommend pausing administrative activities during this time. If you encounter any persistent issues, please contact our support team for assistance.
Dec 6, 20:01 UTC
Dec 9, 2024
Emergency Network Maintenance - AP-South (Singapore)
Completed - The scheduled maintenance has been completed.
Dec 9, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 9, 16:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-South (Singapore) data center beginning 9 December 2024 16:00 (UTC) until 9 December 17:00 (UTC). During this time, users with resources in the AP-South (Singapore) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Dec 9, 12:23 UTC
Emergency Maintenance for Linode Kubernetes Engine (LKE) - US-IAD (Washington)
Completed - The scheduled maintenance has been completed.
Dec 9, 10:44 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 9, 09:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Dec 6, 19:59 UTC
Scheduled - The LKE team will be performing emergency maintenance on Monday December 9th, 2024 from 09:00 UTC to 13:00 UTC. During this window, both the Container Storage Interface (CSI) and the Container Network Interface (CNI) are being restarted. You may experience a brief CNI or CSI interruption while these pods restart. We recommend pausing administrative activities during this time. If you encounter any persistent issues, please contact our support team for assistance.
Dec 6, 19:57 UTC
Connectivity Issue - SE-STO (Stockholm)
Postmortem - Read details
Dec 11, 04:08 UTC
Resolved - We haven’t observed any additional connectivity issues in our Stockholm data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Dec 9, 08:07 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Stockholm 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 9, 03:30 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Stockholm 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, 01:05 UTC
Dec 8, 2024

No incidents reported.

Dec 7, 2024

No incidents reported.

Dec 6, 2024

No incidents reported.

Dec 5, 2024
Dec 4, 2024
Cloud Manager, API, CLI, linode.com Maintenance
Completed - The scheduled maintenance has been completed.
Dec 4, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 4, 14:00 UTC
Scheduled - The Linode Cloud Manager, API, CLI, and linode.com will be undergoing scheduled maintenance between 14:00 UTC and 16:00 UTC, Wednesday, December 4, 2024. During this window, running Linodes and related services should not be disrupted. We will update this status page if we encounter any unexpected issues.
Nov 23, 06:41 UTC
Emergency Network Maintenance - US-East (Newark)
Completed - The scheduled maintenance has been completed.
Dec 4, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 4, 03:00 UTC
Scheduled - We will be performing an emergency network maintenance in our US-East (Newark) data center beginning 4 December 2024 03:00 (UTC) until 4 December 07:00 (UTC). During this time, users with resources in the US-East (Newark) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Dec 3, 19:21 UTC
Dec 3, 2024
Dec 2, 2024
Dec 1, 2024

No incidents reported.

Nov 30, 2024

No incidents reported.

Nov 29, 2024
Service Issue - Object Storage Degraded Performance
Postmortem - Read details
Dec 6, 15:05 UTC
Resolved - After implementing the fix, we haven't observed any additional issues with the Object Storage service in Los Angeles region, 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.
Nov 29, 23:32 UTC
Identified - Our team has identified the issue affecting the Object Storage service in the Los Angeles region. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. If you are experiencing issues, please open a Support ticket for assistance.
Nov 29, 21:23 UTC
Investigating - Our team is investigating an issue affecting the Object Storage service in the Los Angeles region. During this time, users may experience connection timeouts and errors with this service.
Nov 29, 19:58 UTC
Nov 28, 2024
Connectivity Issue - ID-CGK (Jakarta)
Resolved - We haven't observed any additional issues affecting connectivity in our ID-CGK (Jakarta) data center and will now consider this incident resolved as of 20:00 UTC on November 28th, 2024. 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.
Nov 28, 23:04 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our ID-CGK (Jakarta) 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.
Nov 28, 20:37 UTC
Update - We are continuing to work on a fix for this issue. If you are experiencing issues, please open a Support ticket for assistance.
Nov 28, 19:49 UTC
Identified - Our team has identified the issue affecting connectivity in our ID-CGK (Jakarta) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. If you are experiencing issues, please open a Support ticket for assistance.
Nov 28, 16:39 UTC
Investigating - Our team is investigating an issue affecting connectivity in our ID-CGK (Jakarta) 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.
Nov 28, 15:24 UTC
← Incident History Powered by Atlassian Statuspage