All Systems Operational
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
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
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
Managed Databases May 8, 2024 16:15-17:45 UTC
We will be performing a scheduled maintenance on our Managed Databases control plane software. While we do not expect any downtime, brief periods of slow provisioning for new databases might occur.

There will be no loss of connectivity to existing managed databases.

Posted on May 08, 2024 - 16:02 UTC
The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on Tuesday, June 4th, 2024. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Additionally, the Linode Image service in all regions will become unavailable starting at 01:00 UTC until 05:00 UTC on Tuesday, June 4th, 2024. Image creation and image restoration will not be available during this time.

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 Apr 23, 2024 - 18:18 UTC
Past Incidents
May 20, 2024

No incidents reported today.

May 19, 2024

No incidents reported.

May 18, 2024

No incidents reported.

May 17, 2024

No incidents reported.

May 16, 2024

No incidents reported.

May 15, 2024
Completed - The scheduled maintenance has been completed.
May 15, 14:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 14:00 UTC
Scheduled - On Wednesday, May 15th, 2024, at 10:00 EST (May 15th, 2024, at 14:00 UTC), scheduled maintenance will be performed on the Linode Support Ticketing System.

Expected downtime for this maintenance will be about 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.

May 14, 16:45 UTC
May 14, 2024
Completed - The scheduled maintenance has been completed.
May 14, 03:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 14, 02:00 UTC
Scheduled - We will be performing maintenance on our database infrastructure, starting at 02:00 UTC on Tuesday, May 14th, 2024, expected to last 1 hour (until 03:00 UTC, Tuesday, May 14th, 2024). During this period, Cloud Manager and the Linode API should continue to function without interruption, but there is a small possibility that for a few minutes at a time, an action may fail, in which case please retry the action again a few minutes later.
Apr 23, 18:39 UTC
May 13, 2024

No incidents reported.

May 12, 2024

No incidents reported.

May 11, 2024

No incidents reported.

May 10, 2024
Resolved - We haven’t observed any additional connectivity issues in our Washington (IAD) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
May 10, 08:58 UTC
Update - We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.
May 8, 15:10 UTC
Monitoring - Our team has identified the issue affecting connectivity in our Washington, DC (IAD) region to be related to an underlying network issue which has been mitigated. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
May 7, 15:31 UTC
Update - We are continuing to investigate this issue and will provide further updates as soon as they become available.
May 7, 08:26 UTC
Update - We are continuing to investigate this issue.
May 7, 01:43 UTC
Update - We are actively investigating this matter and will provide further updates as soon as more information becomes available.
May 7, 00:19 UTC
Investigating - Our team is actively investigating an ongoing issue impacting the Linode Kubernetes Engine (LKE) in our Washington, DC (IAD) region, specifically concerning DNS resolution and autoscaling. Rest assured, we're diligently working on resolving this issue and will provide further updates as soon as they become available.
May 6, 22:20 UTC
May 9, 2024

No incidents reported.

May 8, 2024
Postmortem - Read details
May 17, 02:29 UTC
Resolved - We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. Please note that customers may see stats gaps for the service issue's impact period - approximately 40 minutes, starting 12:13 UTC on May 8, 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.
May 8, 14:43 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.
May 8, 13:23 UTC
Identified - Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
May 8, 13:10 UTC
Update - We are continuing to investigate the issue that is affecting the Linode Cloud Manager and API, during this time, some users may experience issues when attempting to access Cloud Manager or issue jobs to services on their account including but not limited to Linodes, Block Storage Devices, and Kubernetes Services.
May 8, 12:35 UTC
Investigating - Our team is investigating a service issue that affects the Linode Cloud Manager and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.
May 8, 12:30 UTC
Completed - The scheduled maintenance has been completed.
May 8, 05:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 8, 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, May 8th, 2024. During this window, running Linodes and related services will not be disrupted, but account management access and Support tickets will be unavailable.

Additionally, the Linode Image service in all regions will become unavailable starting at 01:00 UTC until 05:00 UTC on Wednesday, May 8th, 2024. Image creation and image restoration will not be available during this time.

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.

Apr 23, 18:13 UTC
May 7, 2024
Resolved - We haven’t observed any additional connectivity issues in our London (LON1) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
May 7, 20:50 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our London (LON1) 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.
May 7, 17:39 UTC
Investigating - Our team is investigating an issue affecting connectivity in our London (LON1) 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.
May 7, 17:14 UTC
Resolved - We haven’t observed any additional connectivity issues in our London (LON1) data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
May 7, 15:41 UTC
Update - We are continuing to investigate this issue. The impact we are currently experiencing is in our LON1 data center. We will provide another update within the next 60 minutes
May 7, 14:44 UTC
Investigating - Our team is investigating an issue affecting connectivity in our London 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.
May 7, 14:20 UTC
May 6, 2024