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

Linode Status

← Current Status
Connectivity Issue - EU-Central (Frankfurt)
Update - We are continuing to monitor for any further issues.
Nov 05, 2024 - 23:17 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Frankfurt 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 05, 2024 - 07:08 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Frankfurt 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 05, 2024 - 06:20 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
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
Maintenance for Linode Support Ticketing System Nov 7, 2024 18:00-19:00 UTC
On Thursday, November 7th, 2024, at 1:00PM EST (18:00 UTC), scheduled maintenance will be performed on the Linode Support Ticketing System.

Expected downtime for this maintenance will be about 20-30 minutes.

This should not impact the ability to access services or utilize Cloud Manager. Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team.

Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window. As soon as our Support team regains access, we will answer tickets in the order they are received.
Posted on Nov 05, 2024 - 19:08 UTC
Maintenance for Cloud Manager, API, and CLI Nov 20, 2024 03:00-06:00 UTC
The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 03:00 UTC and 06:00 UTC on Wednesday, November 20th, 2024. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Please ensure that you complete critical or important jobs in the Cloud Manager or API before the maintenance window. We will update this status page once this event is complete and Linode customers have full access to all Linode services.

Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team. Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window. As soon as our Support team regains access, we will answer tickets in the order they are received.

Impacts on Current Linode Customers:
Current Linode customers will not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes Create, Remove, Boot, Migrate, Back Up, Shut Down, etc.

The scheduled maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, to include items such as autoscaling, recycling, rebooting, attaching/detaching PVCs, Node Balancer provisioning, as well as the ability to create new clusters. Cluster nodes and running workloads will not be affected.

Impacts on Users Trying to Create Linode Accounts / Awaiting Account Authentication:
While the Linode Cloud Manager is offline during the maintenance period, we are unable to accept requests for new accounts or authenticate accounts for users awaiting full account access.

Thank you for your patience and understanding.
Posted on Oct 31, 2024 - 20:04 UTC
Past Incidents
Nov 6, 2024
Service Issue - Block Storage
Resolved - We haven’t observed any additional issues with the Block Storage service in all our data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Nov 6, 16:27 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.
Nov 6, 15:37 UTC
Identified - Our team has identified the issue affecting the Block Storage service in all our data centers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Nov 6, 15:05 UTC
Investigating - We are investigating an issue affecting the Block Storage service which appears constraint to LKE nodes in all data centers. During this time, users may be unable to attach Block Storage volumes to LKE nodes. We will share additional updates as we have more information.
Nov 6, 14:54 UTC
Nov 5, 2024

Unresolved incident: Connectivity Issue - EU-Central (Frankfurt).

Nov 4, 2024
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 problems, please open a Support ticket for assistance.
Nov 4, 23:06 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our US-IAD (Washington) data center between 16:50-17:25 UTC on November 4, 2024 . 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 4, 18:12 UTC
Linode deployments and Block Storage attachment failing in 11 data centers
Resolved - We have not identified any further issues with the affected services in these regions and will now mark this incident as resolved. If you continue to experience problems, please open a Support ticket for assistance.
Nov 4, 19:45 UTC
Update - We continue to work toward implementing a fix. In the meantime, affected customers may be successful in deploying a Linode or attaching a Block Storage volume to an existing Linode by trying the operation again.
Nov 1, 17:28 UTC
Identified - Our team has identified the issue affecting deployments and Block Storage attachments and is working to implement a fix. We will update again tomorrow (1 November), or as progress is made.
Oct 31, 21:58 UTC
Update - We are continuing to investigate this issue. The appropriate subject matter experts are engaged, should you face issues deploying VMs or try to attach storage to already existing ones across those 11 Data Centers, you may be able to deploy by trying again. We will continue to provide updates as progress is made, until we have a clearer picture about the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.
Oct 30, 23:58 UTC
Update - We are continuing to investigate this issue. The appropriate subject matter experts are engaged, should you face issues deploying Linodes or try to attach storage to already existing ones across those 11 Data Centers, you may be able to deploy by trying again. We will continue to provide updates as progress is made, until we have a clearer picture about the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.
Oct 30, 20:45 UTC
Investigating - We have identified an issue which may prevent the deployment of new Linodes across 11 data centers (Paris, 2 Frankfurt locations, Mumbai, Atlanta, Newark, Chicago, Osaka, Seattle, 2 Singapore locations) or attach storage to already existing ones. We are actively working on creating the action plan to mitigate this issue and will provide another update within the next 60 minutes.
Oct 30, 20:01 UTC
Nov 3, 2024

No incidents reported.

Nov 2, 2024

No incidents reported.

Nov 1, 2024
Oct 31, 2024
Oct 30, 2024
Cloud Manager, API, CLI, linode.com Maintenance
Completed - The scheduled maintenance has been completed.
Oct 30, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 30, 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, October 30, 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.
Oct 22, 19:51 UTC
Scheduled Network Maintenance - EU-Central (Frankfurt)
Resolved - This incident has been resolved.
Oct 30, 13:07 UTC
Investigating - We will be performing an scheduled network maintenance in our EU-Central (Frankfurt) data center from 23:00 (UTC) on Tuesday October 29th until 02:59 (UTC) on Wednesday October 30th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Oct 16, 15:28 UTC
Oct 29, 2024
Managed Database : Hostname display missing for Managed Database clusters
Resolved - This incident has been resolved.
Oct 29, 19:59 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 29, 17:46 UTC
Identified - Display Issue has been identified and fix is in progress, this impacts the display only, Hostname is available through the API.
Oct 29, 15:45 UTC
Investigating - Display Issue has been identified and fix is in progress, this impacts the display only, Hostname is available through the API.
Oct 29, 15:28 UTC
Oct 28, 2024

No incidents reported.

Oct 27, 2024

No incidents reported.

Oct 26, 2024

No incidents reported.

Oct 25, 2024

No incidents reported.

Oct 24, 2024

No incidents reported.

Oct 23, 2024
Object Storage Maintenance BR-GRU (Sao Paulo)
Completed - The scheduled maintenance has been completed.
Oct 23, 20:00 UTC
Update - Scheduled maintenance is currently in progress and has been extended to 20:00 UTC. We will provide updates as necessary.
Oct 23, 18:44 UTC
Update - Scheduled maintenance is currently in progress and has been extended to 19:00 UTC. We will provide updates as necessary.
Oct 23, 17:55 UTC
Update - Scheduled maintenance is currently in progress and has been extended to 18:00 UTC. We will provide updates as necessary.
Oct 23, 16:54 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 23, 15:00 UTC
Scheduled - We will be performing PDU Maintenance in one of our Object Storage cabinets in our Sao Paulo Data Center on October 23rd between 15:00-17:00 UTC. While we do not anticipate any issues, during this time there may be a brief period of failed or delayed requests. We will continue to provide additional updates as this maintenance develops.
Oct 22, 14:10 UTC
Maintenance for Cloud Manager, API, and CLI
Completed - We are no longer performing any maintenance. Operations are expected to be working normally at this time .
Oct 23, 03:08 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 23, 02:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on Wednesday, October 23rd, 2024. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Please ensure that you complete critical or important jobs in the Cloud Manager or API before the maintenance window. We will update this status page once this event is complete and Linode customers have full access to all Linode services.

Customers who need assistance from Linode Support during this time will need to call 855-454-6633 (+1-609-380-7100 outside of the United States) to contact our Support team. Please note that our Support team will not be able to assist with issues related to the Cloud Manager or API, authenticate users to their accounts, or respond to Support tickets for the duration of the maintenance window. As soon as our Support team regains access, we will answer tickets in the order they are received.

Impacts on Current Linode Customers:
Current Linode customers will not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes Create, Remove, Boot, Migrate, Back Up, Shut Down, etc.

The scheduled maintenance will impact the Kubernetes API. Dynamic aspects of LKE that rely on the Linode API will also be impacted, to include items such as autoscaling, recycling, rebooting, attaching/detaching PVCs, Node Balancer provisioning, as well as the ability to create new clusters. Cluster nodes and running workloads will not be affected.

Impacts on Users Trying to Create Linode Accounts / Awaiting Account Authentication:
While the Linode Cloud Manager is offline during the maintenance period, we are unable to accept requests for new accounts or authenticate accounts for users awaiting full account access.

Thank you for your patience and understanding.
Aug 29, 21:30 UTC
← Incident History Powered by Atlassian Statuspage