Update - We will continue to monitor our systems for any further issues this weekend. If you are still experiencing problems, please open a support ticket for assistance.
Jan 10, 2025 - 18:20 UTC
Jan 10, 2025 - 18:20 UTC
Update - We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.
Jan 09, 2025 - 21:09 UTC
Jan 09, 2025 - 21:09 UTC
Monitoring - At this time, we have been able to correct the issues affecting connectivity in our US-IAD (Washington) data center. We will be monitoring this to ensure that it remains stable. In the meantime, we will continue investigating the cause of the network issue experienced during the maintenance. If you are still experiencing issues, please open a Support ticket for assistance.
Jan 09, 2025 - 14:30 UTC
Jan 09, 2025 - 14:30 UTC
Update - The work in the maintenance window caused unexpected network connectivity issues. We are currently working on identifying the cause of that impact as it was not expected. We continue to work on mitigating the issue and will provide more updates as they become available. If you are experiencing issues, please open a Support ticket for assistance.
Jan 09, 2025 - 09:27 UTC
Jan 09, 2025 - 09:27 UTC
Update - We are continuing to work on a fix for this issue. Subsequent updates will be posted as progress is made.
Jan 06, 2025 - 21:05 UTC
Jan 06, 2025 - 21:05 UTC
Identified - Our team has identified the issue affecting connectivity in our US-IAD (Washington) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Jan 02, 2025 - 17:17 UTC
Jan 02, 2025 - 17:17 UTC
Update - We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.
Jan 02, 2025 - 08:06 UTC
Jan 02, 2025 - 08:06 UTC
Update - We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.
Jan 01, 2025 - 23:32 UTC
Jan 01, 2025 - 23:32 UTC
Update - We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.
Jan 01, 2025 - 19:26 UTC
Jan 01, 2025 - 19:26 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. Compute instances running on Premium instances are not impacted by this issue. We will share additional updates as we have more information.
Jan 01, 2025 - 17:43 UTC
Jan 01, 2025 - 17:43 UTC
Service Issue - Block Storage US-ORD (Chicago) US-IAD (Washington, D.C.) and Los Angeles (LAX3)
Subscribe
Monitoring - Our team has identified an issue affecting our Block Storage service in our US-ORD (Chicago), US-IAD (Washington, D.C.) and Los Angeles (LAX3) data centers between the following times:
- Chicago (ORD2): 21:57 UTC to 22:18 UTC
- Washington, D.C. (IAD3): 22:07 UTC to 22:20 UTC
- Los Angeles (LAX3): 21:32 UTC to 21:45 UTC
During this time, users may have experienced slow or failed storage operations for their Block Storage Clients.
We have been able to correct the issues and the service has resumed normal operations. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Jan 10, 2025 - 01:19 UTC
- Chicago (ORD2): 21:57 UTC to 22:18 UTC
- Washington, D.C. (IAD3): 22:07 UTC to 22:20 UTC
- Los Angeles (LAX3): 21:32 UTC to 21:45 UTC
During this time, users may have experienced slow or failed storage operations for their Block Storage Clients.
We have been able to correct the issues and the service has resumed normal operations. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Jan 10, 2025 - 01:19 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 - US-SEA (Seattle)
Jan 13, 2025 12:00-14:00 UTC
We will be performing an emergency network maintenance in our US-SEA region on Monday, January 13, 2025 from 12:00 UTC to 14:00 UTC. While we do not expect any impact, there may be brief periods of packet loss.
Posted on Jan 11, 2025 - 16:39 UTC
Posted on Jan 11, 2025 - 16:39 UTC
Emergency Network Maintenance - AP-South (Singapore)
Jan 13, 2025 17:00-21:00 UTC
We will be performing an emergency network maintenance in our AP-South (Singapore) data center beginning 13 January 2025 17:00 (UTC) until 13 January 2025 21: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
Posted on Jan 10, 2025 - 13:22 UTC
Posted on Jan 10, 2025 - 13:22 UTC
Emergency Network Maintenance - JP-OSA (Osaka)
Jan 13, 2025 20:00-22:00 UTC
We will be performing an emergency network maintenance in our JP-OSA region on Monday, January 13, 2025 from 20:00 UTC to 22:00 UTC. While we do not expect any impact, there may be brief periods of packet loss.
Posted on Jan 11, 2025 - 16:41 UTC
Posted on Jan 11, 2025 - 16:41 UTC
Maintenance for Cloud Manager, API, and CLI
Jan 22, 2025 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, January 22nd, 2025. 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 Jan 07, 2025 - 17:38 UTC
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 Jan 07, 2025 - 17:38 UTC
Cloud Manager, API, CLI, linode.com Maintenance
Feb 4, 2025 14:00-16:00 UTC
The Linode Cloud Manager, API, CLI, and linode.com will be undergoing scheduled maintenance between 14:00 UTC and 16:00 UTC, Tuesday, February 4, 2025. During this window, running Linodes and related services should not be disrupted. We will update this status page if we encounter any unexpected issues.
Posted on Jan 09, 2025 - 11:11 UTC
Posted on Jan 09, 2025 - 11:11 UTC
Cloud Manager, API, CLI, linode.com Maintenance
Feb 6, 2025 14:00-16:00 UTC
The Linode Cloud Manager, API, CLI, and linode.com will be undergoing scheduled maintenance between 14:00 UTC and 16:00 UTC, Tuesday, February 6, 2025. During this window, running Linodes and related services should not be disrupted. We will update this status page if we encounter any unexpected issues.
Posted on Jan 09, 2025 - 11:08 UTC
Posted on Jan 09, 2025 - 11:08 UTC