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
Maintenance for LISH Feb 22, 2024 14:00-16:00 UTC
We will be performing maintenance on LISH Service limited to LISH SSH (not Weblish or Glish), starting at 14:00 UTC on Feb 22nd, expected to last two hours (until 16:00 UTC, Feb 22nd). Most LISH SSH connections continuously in operation over 14 days at the time of this maintenance window will be closed, in order to improve the service. LISH SSH connections opened within 14 days will not be affected. Weblish and Glish connections will not be affected. Any user with an affected LISH SSH connection may immediately reconnect. This necessary reconnection for some users is expected to be the only effect of this maintenance window.
Posted on Jan 12, 2024 - 20:56 UTC
We will be performing an emergency network maintenance in our EU-West (London, UK) data center from 22:00 (UTC) until 23:59 (UTC) on Thursday, February 22nd. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Posted on Feb 21, 2024 - 15:54 UTC
On Thursday, February 22nd, 2024, at 22:00 EST (February 23rd, 2024, at 03:00 UTC), scheduled maintenance will be performed on the Linode Support Ticketing System. Expected downtime for this maintenance will be about 15-20 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 Feb 16, 2024 - 19:08 UTC
Maintenance for Login, Alerts, Statistics Feb 27, 2024 14:30-16:30 UTC
We will be performing maintenance on Linode subsystems that affect Login, Alerts, and Statistics, starting at 14:30 UTC on Feb 27th, expected to last two hours (until 16:30 UTC, Feb 27th). During this period, it is not expected that any functionality will be interrupted. However, there is a small possibility that, for a few minutes at a time, Linode dashboard statistics and service alerts become delayed or unresponsive before recovering. Additionally, there is a small chance new logins to the Cloud Manager may not complete for a few minutes during this maintenance, and may need to be retried. Active sessions will not be impacted.
Posted on Jan 19, 2024 - 20:21 UTC
The Linode Cloud Manager, API, CLI, and linode.com 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. The www.linode.com website will also not be reachable during this window.

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.

Posted on Jan 26, 2024 - 16:37 UTC
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.
Posted on Jan 26, 2024 - 16:39 UTC
Past Incidents
Feb 22, 2024

No incidents reported today.

Feb 21, 2024

No incidents reported.

Feb 20, 2024

No incidents reported.

Feb 19, 2024

No incidents reported.

Feb 18, 2024
Postmortem - Read details
Feb 21, 13:29 UTC
Resolved - We haven't observed any reoccurrence of the issue with Linode.com, and will now consider this incident resolved. 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.
Feb 18, 15:28 UTC
Update - We are continuing to monitor the situation with Linode.com to ensure that there are no additional issues, and connectivity remains stable.


Please open a Support ticket or give us a call at 855-454-6633 (+1-609-380-7100 Intl.) if you are experiencing any issues.

Feb 16, 23:23 UTC
Monitoring - At this time, our team has implemented a fix to address the service issue affecting Linode.com. We will be monitoring the results for the next 24 hours to ensure that connectivity remains stable.

If you are still experiencing issues please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

Feb 15, 21:22 UTC
Update - Our team is still investigating the issue affecting Linode.com. We will continue to share additional updates as we have more information.

Please open a Support ticket or give us a call at 855-454-6633 (+1-609-380-7100 Intl.) if you are experiencing any issues.

Feb 15, 18:35 UTC
Update - Our team is still actively investigating the service issue affecting Linode.com. We will share additional updates as we have more information.

Please open a Support ticket or give us a call at 855-454-6633 (+1-609-380-7100 Intl.) if you are experiencing any issues.

Feb 14, 01:57 UTC
Investigating - Our team is investigating a service issue that affected Linode.com. The service issue was experienced from 22:32 UTC to 23:30 UTC on February 13, 2024. A fix has been implemented and we are monitoring the results.

Please open a Support ticket or give us a call at 855-454-6633 (+1-609-380-7100 Intl.) if you need immediate assistance.

Feb 14, 00:50 UTC
Feb 17, 2024

No incidents reported.

Feb 16, 2024
Feb 15, 2024
Feb 14, 2024
Feb 13, 2024

No incidents reported.

Feb 12, 2024

No incidents reported.

Feb 11, 2024

No incidents reported.

Feb 10, 2024

No incidents reported.

Feb 9, 2024

No incidents reported.

Feb 8, 2024
Postmortem - Read details
Feb 14, 17:34 UTC
Resolved - We are pleased to share that the technical issue affecting email deliverability to customers using Microsoft domains has been resolved. If you were experiencing difficulties receiving messages from Linode.com, including Outlook, Hotmail, and MSN, you should now be able to do so without any problems.

If you are still encountering any issues or have further concerns, please contact Support for assistance.

Feb 8, 18:46 UTC
Update - Our team is currently working with both internal stakeholders and the Microsoft team to address email delivery issues. We will provide further information as we progress.
Feb 7, 12:24 UTC
Investigating - We are aware of an issue impacting the ability of customers using Microsoft domains to receive messages sent from Linode.com (including Outlook, Hotmail, and MSN). Our Team is actively investigating a fix for this issue, and we will update here once we have more information. If you are unable to receive account-related emails, and/or have issues accessing your account, please give us a call at 855-454-6633 (+1-609-380-7100 for international/non-US callers). When calling, please be prepared to provide identifying information to prove ownership of the account.
Feb 4, 15:09 UTC