Linode Status

Current Status
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
We will be performing an emergency network maintenance in our US-Central (Dallas) data center from 05:00 (UTC) until 09:00 (UTC) on Wednesday, March 20th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Posted on Mar 18, 2024 - 16:29 UTC
We will be performing an emergency network maintenance in our AP-West (Mumbai) data center from 17:30 (UTC) until 20:30 (UTC) on Wednesday, March 20th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Posted on Mar 12, 2024 - 12:11 UTC
The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on Wednesday, April 3rd, 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 AM UTC on Wednesday, April 3rd, 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.

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 Feb 29, 2024 - 16:16 UTC
Past Incidents
Mar 19, 2024

No incidents reported today.

Mar 18, 2024

No incidents reported.

Mar 17, 2024

No incidents reported.

Mar 16, 2024

No incidents reported.

Mar 15, 2024

No incidents reported.

Mar 14, 2024

No incidents reported.

Mar 13, 2024
Completed - The scheduled maintenance has been completed.
Mar 13, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 13, 16:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-Southeast (Sydney) data center from 16:00 (UTC) until 20:00 (UTC) on Wednesday, March 13th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Mar 6, 16:44 UTC
Completed - The scheduled maintenance has been completed.
Mar 13, 17:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 13, 16:00 UTC
Scheduled - 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.

Mar 12, 20:27 UTC
Completed - The scheduled maintenance has been completed.
Mar 13, 08:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 13, 04:00 UTC
Scheduled - We will be performing an emergency network maintenance in our US-East (Newark) data center from 04:00 (UTC) until 08:00 (UTC) on Wednesday, March 13th. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Mar 11, 16:46 UTC
Mar 12, 2024
Completed - The scheduled maintenance has been completed.
Mar 12, 15:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 12, 13:30 UTC
Scheduled - We will be performing maintenance on DNS Manager, starting at 13:30 UTC on Mar 12th, expected to last two hours (until 15:30 UTC, Mar 12th). During this period, DNS answers will continue to be served by DNS infrastructure, but there is a small possibility that propagation of new DNS zones or changes to existing zones to our resolvers may be delayed by a few minutes. Also during this period, the Linode Community Site is expected to continue to function normally, but there is a small possibility that it becomes unavailable for a few minutes, in which case please revisit after a few minutes. Lastly, the Metadata Service is expected to continue to function normally, but there is a small possibility that it cannot process API requests or otherwise delays actions for a few minutes at a time, in which case, please wait a few minutes and retry.
Jan 26, 16:39 UTC
Mar 11, 2024

No incidents reported.

Mar 10, 2024

No incidents reported.

Mar 9, 2024

No incidents reported.

Mar 8, 2024
Postmortem - Read details
Mar 13, 13:33 UTC
Resolved - We haven’t observed any additional issues with the Block Storage service in Fremont, and will now consider this incident resolved.

If you continue to experience issues, please open a Support ticket for assistance.

Mar 8, 18:25 UTC
Monitoring - Our team has identified an issue affecting Block Storage service in our Fremont data center, also affecting our Manage Databases Service. A fix has been implemented, and we will now be monitoring for any further issues.

If you continue to experience problems, please open a Support ticket for assistance.

Mar 7, 23:07 UTC
Mar 7, 2024
Mar 6, 2024
Completed - The scheduled maintenance has been completed.
Mar 6, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 6, 03:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 03:00 UTC and 06:00 UTC on Wednesday, March 6th, 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 02:00 UTC until 06:00 AM UTC on Wednesday, February 7th, 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.

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.

Jan 26, 16:37 UTC
Mar 5, 2024
Postmortem - Read details
Mar 18, 18:42 UTC
Resolved - We haven’t observed any additional issues with the Block Storage service during our monitoring, and will now consider this incident resolved.

If you continue to experience problems, please open a Support ticket for assistance.

Mar 5, 23:25 UTC
Monitoring - Testing is now complete. Our team deployed a fix to address the impact caused by our previous change. 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.
Mar 5, 18:04 UTC
Identified - We have identified the cause for unexpected limitations that were put in place that resulted in the prevention of adding additional services. Our team is currently working on addressing this, which will include testing. Due to the time required for this testing, we do not anticipate an update for another two hours. That said, we will update this page once we have more information to share.
Mar 5, 16:52 UTC
Investigating - Our team is investigating an issue affecting the Block Storage service on accounts with large data pools (100TB or greater). During this time, users may experience errors creating further volumes. We will share additional updates as we have more information.
Mar 5, 13:19 UTC