Connectivity Issue - JP-OSA (Osaka)
Monitoring - Our team is aware of an issue that affected connectivity in our JP-OSA (Osaka) data center. The issue started on November 18, 2024. During this time, users experienced intermittent connection timeouts and errors for all services deployed in this data center. At this time we have been able to correct the issues affecting connectivity in our JP-OSA (Osaka) 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.
Nov 20, 2024 - 19:03 UTC
Connectivity Issue - EU-Central (Frankfurt)
Update - We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.
Nov 18, 2024 - 14:09 UTC
Update - We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.
Nov 11, 2024 - 09:28 UTC
Update - We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.
Nov 07, 2024 - 19:53 UTC
Update - We are continuing to monitor for any further issues.
Nov 05, 2024 - 23:17 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Frankfurt 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.
Nov 05, 2024 - 07:08 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Frankfurt 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.
Nov 05, 2024 - 06:20 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
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 - EU-Central (Frankfurt) Nov 20, 2024 23:00 - Nov 21, 2024 03:00 UTC
Scheduled - We will be performing an emergency network maintenance in our EU-Central (Frankfurt) data center beginning 20 November 2024 23:00 (UTC) until 21 November 03:00 (UTC). During this time, users with resources in the EU-Central (Frankfurt) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Nov 20, 2024 - 17:05 UTC
Past Incidents
Nov 20, 2024
Maintenance for Cloud Manager, API, and CLI
Completed - The scheduled maintenance has been completed.
Nov 20, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 20, 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, November 20th, 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.
Oct 31, 20:04 UTC
Nov 19, 2024

No incidents reported.

Nov 18, 2024

Unresolved incident: Connectivity Issue - EU-Central (Frankfurt).

Nov 17, 2024

No incidents reported.

Nov 16, 2024

No incidents reported.

Nov 15, 2024

No incidents reported.

Nov 14, 2024
Linodes failing to boot and apply firewall changes in all Data Centers
Resolved - We haven't observed any additional issues causing boot failures for Linodes as well as inability to make changes to Cloud Firewall rules, 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.
Nov 14, 23:42 UTC
Monitoring - As of 21:19 UTC we have been able to correct the issue causing boot failures for Linodes as well as the inability to make changes to Cloud Firewall rules. 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.
Nov 14, 21:43 UTC
Identified - As of 19:46 UTC, we have been able to fix the issue causing the inability to boot Linodes and those booted Linodes are able to apply changes to Cloud Firewall rules. We are actively working to fix the Cloud Firewall rules that were deployed during the impact window as they are not applied at the moment. We will share additional updates as we have more information.
Nov 14, 20:32 UTC
Update - To add on to our previous post, customers may have issues with creating/recycling Linode Kubernetes Engine nodes and/or deploying Managed Databases as a result of this issue. Any Cloud Firewalls used along with those services would likely be unable to apply rule changes, as well.
Nov 14, 19:45 UTC
Investigating - At around 17:00 UTC on November 14th after a change we started noticing Host job failures across several Data Centers (including London, Dallas and Atlanta) specifically, some Linodes are failing to boot, and those which fail to boot may also be unable to apply changes to Cloud Firewall rules. Our team is investigating a service issue. We will share additional updates as we have more information.
Nov 14, 19:38 UTC
Nov 13, 2024

No incidents reported.

Nov 12, 2024

No incidents reported.

Nov 11, 2024
Nov 10, 2024

No incidents reported.

Nov 9, 2024

No incidents reported.

Nov 8, 2024

No incidents reported.

Nov 7, 2024
Maintenance for Linode Support Ticketing System
Completed - The scheduled maintenance has been completed.
Nov 7, 19:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 7, 18:00 UTC
Scheduled - On Thursday, November 7th, 2024, at 1:00PM EST (18:00 UTC), scheduled maintenance will be performed on the Linode Support Ticketing System.

Expected downtime for this maintenance will be about 20-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.
Nov 5, 19:08 UTC
Nov 6, 2024
Service Issue - Block Storage
Postmortem - Read details
Nov 12, 14:03 UTC
Resolved - We haven’t observed any additional issues with the Block Storage service in all our data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Nov 6, 16:27 UTC
Monitoring - 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.
Nov 6, 15:37 UTC
Identified - Our team has identified the issue affecting the Block Storage service in all our data centers. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Nov 6, 15:05 UTC
Investigating - We are investigating an issue affecting the Block Storage service which appears constraint to LKE nodes in all data centers. During this time, users may be unable to attach Block Storage volumes to LKE nodes. We will share additional updates as we have more information.
Nov 6, 14:54 UTC
← Incident History Powered by Atlassian Statuspage