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
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
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 Cloud Manager, API, and CLI
Oct 23, 2024 02:00-05:00 UTC
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.
Posted on Aug 29, 2024 - 21:30 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 Aug 29, 2024 - 21:30 UTC