Service Issue - LKE and Object Storage - All Regions
Update - Our subject matter experts are continuing to work on mitigating the impact. The Linode Kubernetes Engine (LKE) service has been largely restored, and we continue to work on mitigating the impact in the London and Chicago regions. Mitigation efforts for Object Storage E2/E3 endpoints are ongoing and will require additional time to fully resolve the issue. We appreciate your patience and will provide further updates as progress continues.
Jul 18, 2025 - 18:43 UTC
Update - We are continuing to work on mitigating the impact of this incident. The Linode Kubernetes Engine (LKE) service has been largely restored and is operating normally for most customers. Mitigation efforts for Object Storage E2/E3 endpoints are ongoing and will require additional time to fully resolve. We appreciate your patience and will provide further updates as progress continues.
Jul 18, 2025 - 14:10 UTC
Update - Our subject matter experts are actively working on the recovery of the impacted Object Storage E2/E3 endpoints. We will share further updates as we make progress. We apologize for the impact and thank you for your patience and continued support. If you have any questions, please contact our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 18, 2025 - 09:20 UTC
Update - Current Status
Our teams are actively working to resolve issues impacting Object Storage E2 and E3 endpoints. While Standard (E0/E1) endpoints were not affected, we are working on system recovery for all E2 and E3 endpoints. These issues are being prioritized, and expert teams are engaged in resolving the impact.

Object Storage E2 and E3 Endpoint Recovery Plan
We are employing an incremental approach to ensure a safe and methodical recovery.

> Recovery order by Datacenter: We understand that you may have questions about the recovery process for your specific region. At this time, we are taking a step-by-step approach, and as a result, we do not yet have a determined order for datacenter recovery. Our focus is on restoring systems safely, working to minimize impact across all customers. We will share updates regularly as recovery progresses and will notify you promptly once we can confirm timelines for your specific E2/E3 Endpoint region(s).
> Testing and Validation: To ensure stability and avoid service disruptions, all systems will undergo extensive testing prior to resuming regular operations.

Impact and Timelines
While we are devoting 24/7 engineering resources to this recovery operation, complete resolution will depend on the results of our ongoing diagnostics. Full recovery for affected regions may require multiple days and our teams are looking for ways to optimize and parallelize recovery operations. As we make further progress over the next few hours, we expect to be able to provide more specific updates on estimated recovery times.

Our Commitment
We deeply regret the impact being caused by this disruption and want to assure you of our commitment to restoring full operations as quickly and safely as possible. We will keep you updated with progress and key milestones throughout the recovery process. If you have any questions or concerns, please do not hesitate to reach out to our support team at support@linode.com or call us at +1-855-454-6633 (US) or +1-609-380-7100 (Global) for assistance.
Jul 18, 2025 - 02:39 UTC
Identified - Affected services have begun to come back online. Currently, the following services are up:
• Creating and restoring images to Linodes
• LKE and LKE-Enterprise new cluster provisioning, except in London
• Managed Databases

We are working to restore service to all affected Object Storage E2 and E3 endpoints and will continue to provide updates as more services come back online.
Jul 18, 2025 - 01:06 UTC
Update - We are continuing to investigate this issue. The appropriate subject matter experts are engaged. We will continue to provide hourly updates until we have a clearer picture about the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.
Jul 17, 2025 - 23:43 UTC
Update - We have confirmed that the issue is impacting the following services:
• Object Storage Key and bucket management using the Linode Cloud Manager and Linode APIv4
• The following Object Storage E2 and E3 endpoints are down:
• jp-osa-1.linodeobjects.com
• us-sea-9.linodeobjects.com
• au-mel-1.linodeobjects.com
• gb-lon-1.linodeobjects.com
• in-bom-1.linodeobjects.com
• jp-tyo-1.linodeobjects.com
• us-iad-13.linodeobjects.com
• us-ord-10.linodeobjects.com
• de-fra-1.linodeobjects.com
• sg-sin-1.linodeobjects.com
• Linode Kubernetes Engine (LKE) and LKE-Enterprise
• Creating clusters
• Restoring clusters from a backup
• Creating and restoring images, including deployment of Linodes from images
• Managed Databases
• Provisioning new clusters
• Resizing existing clusters
• Resuming a suspended cluster
• Restoring existing clusters from backup
• Multi-node clusters will be able to recover from a primary node failure automatically as long as cluster standby Linodes are online
• Automatic recreation of failed nodes is unavailable at this time


We will continue to share updates as we have more information.
Jul 17, 2025 - 22:32 UTC
Investigating - Our team is investigating an emerging service issue affecting LKE and Object Storage in all regions. We will share additional updates as we have more information.
Jul 17, 2025 - 20:35 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 (São 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
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) 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
BR-GRU (São Paulo) Backups Operational
NL-AMS (Amsterdam) Backups Operational
ES-MAD (Madrid) Backups Operational
IT-MIL (Milan) Backups Operational
US-MIA (Miami) Backups Operational
ID-CGK (Jakarta) Backups Operational
US-LAX (Los Angeles) Backups Operational
GB-LON (London 2) Backups Operational
AU-MEL (Melbourne) Backups Operational
IN-BOM-2 (Mumbai 2) Backups Operational
DE-FRA-2 (Frankfurt 2) Backups Operational
SG-SIN-2 (Singapore 2) Backups Operational
JP-TYO-3 (Tokyo) 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
BR-GRU (São Paulo) Block Storage Operational
NL-AMS (Amsterdam) Block Storage Operational
ES-MAD (Madrid) Block Storage Operational
IT-MIL (Milan) Block Storage Operational
US-MIA (Miami) Block Storage Operational
ID-CGK (Jakarta) Block Storage Operational
US-LAX (Los Angeles) Block Storage Operational
GB-LON (London 2) Block Storage Operational
AU-MEL (Melbourne) Block Storage Operational
IN-BOM-2 (Mumbai 2) Block Storage Operational
DE-FRA-2 (Frankfurt 2) Block Storage Operational
SG-SIN-2 (Singapore 2) Block Storage Operational
JP-TYO-3 (Tokyo 3) 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
BR-GRU (São Paulo) NodeBalancers Operational
NL-AMS (Amsterdam) NodeBalancers Operational
ES-MAD (Madrid) NodeBalancers Operational
IT-MIL (Milan) NodeBalancers Operational
US-MIA (Miami) NodeBalancers Operational
ID-CGK (Jakarta) NodeBalancers Operational
US-LAX (Los Angeles) NodeBalancers Operational
GB-LON (London 2) NodeBalancers Operational
AU-MEL (Melbourne) NodeBalancers Operational
IN-BOM-2 (Mumbai 2) NodeBalancers Operational
DE-FRA-2 (Frankfurt 2) NodeBalancers Operational
SG-SIN-2 (Singapore 2) NodeBalancers Operational
JP-TYO-3 (Tokyo 3) NodeBalancers Operational
Object Storage Partial Outage
US-East (Newark) Object Storage Operational
US-Southeast (Atlanta) Object Storage Operational
US-IAD (Washington) Object Storage Operational
US-ORD (Chicago) Object Storage Partial Outage
EU-Central (Frankfurt) Object Storage Partial Outage
AP-South (Singapore) Object Storage Partial Outage
FR-PAR (Paris) Object Storage Operational
SE-STO (Stockholm) Object Storage Operational
US-SEA (Seattle) Object Storage Partial Outage
JP-OSA (Osaka) Object Storage Operational
IN-MAA (Chennai) Object Storage Operational
ID-CGK (Jakarta) Object Storage Operational
BR-GRU (Sao Paulo) Object Storage Operational
ES-MAD (Madrid) Object Storage Operational
GB-LON (London 2) Partial Outage
AU-MEL (Melbourne) Partial Outage
NL-AMS (Amsterdam) Object Storage Operational
IT-MIL (Milan) Object Storage Operational
US-MIA (Miami) Object Storage Operational
US-LAX (Los Angeles) Object Storage Operational
GB-LON (London 2) Object Storage Partial Outage
AU-MEL (Melbourne) Object Storage Partial Outage
IN-BOM-2 (Mumbai 2) Object Storage Partial Outage
DE-FRA-2 (Frankfurt 2) Object Storage Partial Outage
SG-SIN-2 (Singapore 2) Object Storage Partial Outage
JP-TYO-3 (Tokyo 3) Object Storage Partial Outage
Linode Kubernetes Engine Partial Outage
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 Partial Outage
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) Linode Kubernetes Engine Operational
BR-GRU (São Paulo) Linode Kubernetes Engine Operational
NL-AMS (Amsterdam) Linode Kubernetes Engine Operational
ES-MAD (Madrid) Linode Kubernetes Engine Operational
IT-MIL (Milan) Linode Kubernetes Engine Operational
US-MIA (Miami) Linode Kubernetes Engine Operational
US-LAX (Los Angeles) Linode Kubernetes Engine Operational
GB-LON (London 2) Linode Kubernetes Engine Partial Outage
AU-MEL (Melbourne) Linode Kubernetes Engine Operational
IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine Operational
DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine Operational
SG-SIN-2 (Singapore 2) Linode Kubernetes Engine Operational
JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine Operational
Metadata Service 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 (São 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
ZA-JNB (Johannesburg) Operational
NZ-AKL (Auckland) Operational
CO-BOG (Bogota) Operational
US-DEN (Denver) Operational
DE-HAM (Hamburg) Operational
US-HOU (Houston) Operational
MY-KUL (Kuala Lumpur) Operational
FR-MRS (Marseille) Operational
MX-QRO (Queretaro) Operational
CL-SCL (Santiago) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Maintenance for Linode Cloud Manager, API, and CLI Jul 23, 2025 02:00-04:00 UTC

The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 04:00 UTC on July 23, 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, including 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 Jul 07, 2025 - 20:22 UTC

Maintenance for Linode Support Ticketing System Jul 24, 2025 03:00-04:00 UTC

On Wednesday, July 23rd at 11:00PM EDT (Thursday, July 24th at 3:00AM UTC), scheduled maintenance will be performed on the Linode Support Ticketing System. Expected downtime for this maintenance will be about 60 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 Jul 15, 2025 - 21:08 UTC

Scheduled Network Maintenance(Cloud Firewall2) - US-MIA (Miami) Jul 24, 2025 04:00-09:00 UTC

We will perform network maintenance at the US-MIA (Miami) data center on July 24, 2025, from 04:00 UTC to 09:00 UTC. While we do not anticipate any impact, there may be brief connectivity disruptions during this window, and the firewall will be offline for a short period.
Posted on Jul 18, 2025 - 06:43 UTC

Scheduled Network Maintenance(Cloud Firewall2) - APAC Region Jul 31, 2025 12:00-18:00 UTC

We will be performing network maintenance at the following data centers on July 31, 2025, from 12:00 UTC to 18:00 UTC: -
AP-South (Singapore), AP-Northeast-2 (Tokyo 2), AP-West (Mumbai), AP-Southeast (Sydney), JP-OSA (Osaka), IN-MAA (Chennai), ID-CGK (Jakarta), AU-MEL (Melbourne), IN-BOM-2 (Mumbai 2), SG-SIN-2 (Singapore 2), JP-TYO-3 (Tokyo 3) .

While we do not anticipate any impact, there may be brief connectivity disruptions during this window, and the firewall will be offline for a short period.
Posted on Jul 18, 2025 - 09:16 UTC

Scheduled Network Maintenance - US-IAD (Washington) Aug 5, 2025 04:00-12:00 UTC

We will be performing a scheduled network maintenance in our US-IAD (Washington) data center from 04:00 (UTC) until 12:00 (UTC) on Tuesday, August 5th. Brief network outages and the possibility of live migrations for linodes are expected.
Posted on Jul 18, 2025 - 19:04 UTC
Jul 18, 2025

Unresolved incident: Service Issue - LKE and Object Storage - All Regions.

Jul 17, 2025
Scheduled Network Maintenance(Cloud Firewall2) -IT-MIL (Milan)
Completed - The scheduled maintenance has been completed.
Jul 17, 23:55 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 17, 19:00 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 17, 08:07 UTC
Scheduled - We will be performing network maintenance in IT-MIL (Milan) data center between 19:00 UTC and 23:55 UTC on July 17, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions and there will be no firewall for a short period of time.
Jul 17, 06:27 UTC
The Linode Cloud Manager Failover Test
Completed - The scheduled maintenance has been completed.
Jul 17, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 17, 13:00 UTC
Scheduled - The Linode Cloud Manager and API will undergo scheduled failover testing between 13:00 UTC and 14:00 UTC on July 17, 2025. During this window, the cloud manager service may be impacted briefly (<5min) during the failover process. We will update this status page if we encounter any unexpected issues.
Jul 15, 18:51 UTC
Jul 16, 2025

No incidents reported.

Jul 15, 2025
Linode Cloud Manager scheduled maintenance for failover testing
Postmortem - Read details
Jul 15, 18:46 UTC
Completed - The scheduled maintenance has been completed.
Jul 15, 15:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 14:00 UTC
Update - The Linode Cloud Manager will undergo scheduled failover testing
Jul 11, 18:27 UTC
Scheduled - The Linode Cloud Manager and API will undergo scheduled failover testing between 14:00 UTC and 15:30 UTC on July 15, 2025. During this window, the cloud manager service should not be disrupted. We will update this status page if we encounter any unexpected issues.
Jul 11, 18:26 UTC
Maintenance for Linode Cloud Manager Login and API
Completed - The scheduled maintenance has been completed.
Jul 15, 06:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 15, 05:30 UTC
Update - We will be undergoing scheduled maintenance during this time.
Jul 14, 13:55 UTC
Scheduled - The Linode Cloud Manager Login and API will be undergoing scheduled maintenance between 13:30:00 UTC and 15:00:00 UTC, July 15, 2025. During this window service may disrupted. We will update this status page if we encounter any unexpected issues.
Jul 8, 13:08 UTC
Service Issue - Connectivity - US-LAX
Resolved - We haven’t observed any additional connectivity issues in our Los Angeles data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jul 15, 03:01 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our Los Angeles, CA data center. The issue started at approximately 18:22 UTC and was mitigated at 19:00 UTC for our IPv4 traffic and at 19:08 UTC for our IPv6 traffic. During the impact window customers could have notice slowness, timeouts and/or connection errors.
We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Jul 14, 19:57 UTC
Investigating - Our team is investigating an emerging service issue affecting connectivity to our Los Angeles, CA region. We will share additional updates as we have more information.
Jul 14, 19:09 UTC
Jul 14, 2025
Jul 13, 2025

No incidents reported.

Jul 12, 2025
Emerging Service Issue - OBJ Unavailable via Cloud Manager and API
Resolved - This incident has been resolved.
Jul 12, 22:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 12, 21:42 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 12, 21:35 UTC
Update - We are continuing to investigate this issue.
Jul 12, 21:27 UTC
Update - We are continuing to investigate this issue.
Jul 12, 20:27 UTC
Update - We are continuing to investigate this issue. Object Storage buckets could still be created and managed successfully using tools such as s3cmd and Cyberduck as a workaround.
Jul 12, 19:23 UTC
Investigating - We are aware of an issue preventing management of Object Storage using Cloud Manager and the API. This includes Object Storage buckets as well as access keys. We will share additional updates as we have more information.
Jul 12, 17:46 UTC
Jul 11, 2025
Connectivity Issue - Dallas: 1 (INVESTIGATING)
Resolved - It appears the issue was caused by a temporary network disruption outside our infrastructure. We can confirm that everything is currently stable and functioning normally.
Jul 11, 09:36 UTC
Update - We have seen a recent improvement in the situation affecting our Dallas data center, though we are continuing to investigate the root cause of this issue. If you are still experiencing additional problems, please open a Support ticket from your Cloud Manager.
Jul 11, 03:16 UTC
Investigating - Our team is investigating an issue affecting networking in our Dallas 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.
Jul 11, 01:35 UTC
Jul 10, 2025
LKE clusters inaccessible in OSA1
Postmortem - Read details
Jul 16, 04:17 UTC
Resolved - We haven’t observed any additional issues with the LKE service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jul 10, 18:17 UTC
Monitoring - At this time we have been able to correct the issues affecting the LKE service in the Osaka, Japan region. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
Jul 10, 17:17 UTC
Update - Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Jul 10, 16:49 UTC
Identified - Our team has identified the issue affecting the LKE service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Jul 10, 15:14 UTC
Update - We are continuing to investigate this issue with Linode Kubernetes Engine in the Osaka, Japan region.
Jul 10, 11:09 UTC
Update - We are continuing to investigate this issue with Linode Kubernetes Engine in the Osaka, Japan region.
Jul 10, 10:08 UTC
Investigating - We are aware of an issue preventing access to LKE clusters in OSA1 and are actively working to resolve it
Jul 10, 09:05 UTC
Jul 9, 2025

No incidents reported.

Jul 8, 2025
Maintenance for Linode Cloud Manager, API, and CLI
Completed - The scheduled maintenance has been completed.
Jul 8, 22:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 8, 21:00 UTC
Update - The scheduled maintenance for the Linode Cloud Manager, API, and CLI has been rescheduled to take place between 21:00 UTC and 22:00 UTC on July 8, 2025. No service disruption is expected during this window. We will provide updates on this status page if any unexpected issues occur.
Jul 8, 11:54 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 12:00:00 UTC and 13:00:00 UTC, July 8, 2025. During this window service should not be disrupted. We will update this status page if we encounter any unexpected issues.
Jun 24, 23:11 UTC
Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage