View all products
Compute
Storage
Networking
Databases
Services
Solutions
Pricing
Library
Technical Resources
Community
Marketplace
What's New

Linode Status

← Current Status
Service Issue - Cloud Manager and API
Update - We are continuing to monitor for any further issues.
Oct 08, 2025 - 20:53 UTC
Monitoring - A database maintenance was performed and we are currently monitoring the results. If you are still experiencing issues, please open a Support ticket for assistance.
Oct 02, 2025 - 08:00 UTC
Update - We are continuing to investigate this issue.
Oct 02, 2025 - 00:05 UTC
Investigating - Our team is investigating a service issue that intermittently triggers 5XX responses in the Cloud Manager (https://cloud.linode.com/) and API request failures for brief periods. We will share additional updates as we have more information.
Oct 01, 2025 - 22:05 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 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) Object Storage Operational
BR-GRU (Sao Paulo) Object Storage Operational
ES-MAD (Madrid) Object Storage Operational
GB-LON (London 2) Operational
AU-MEL (Melbourne) Operational
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 Operational
AU-MEL (Melbourne) Object Storage Operational
IN-BOM-2 (Mumbai 2) Object Storage Operational
DE-FRA-2 (Frankfurt 2) Object Storage Operational
SG-SIN-2 (Singapore 2) Object Storage Operational
JP-TYO-3 (Tokyo 3) 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) 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 Operational
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

Scheduled Network Maintenance - NL-AMS (Amsterdam) Oct 9, 2025 01:00-05:00 UTC

We will be performing network maintenance at NL-AMS (Amsterdam) on October 9th from 01:00 UTC to 05:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Posted on Sep 10, 2025 - 21:54 UTC

Scheduled Network Maintenance - ID-CGK (Jakarta) Oct 13, 2025 19:00-23:00 UTC

We will be performing network maintenance at ID-CGK (Jakarta) on October 13th from 19:00 UTC to 23:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Posted on Sep 10, 2025 - 21:56 UTC

Network Maintenance - Washington (US-IAD) Oct 14, 2025 04:00-10:00 UTC

On Tuesday, October 14th at approximately 04:00 UTC to 10:00 UTC, we will be performing maintenance on the border routers in our Washington (US-IAD) region to complete the second part of an upgrade. The benefit of this upgrade is that it will help reduce bottlenecks and allow for greater capacity across the region. During this maintenance, there may be brief periods of packet loss and latency.
Posted on Sep 29, 2025 - 18:22 UTC

Scheduled Network Maintenance - SG-SIN-2 (Singapore 2) Oct 15, 2025 20:00 - Oct 16, 2025 00:00 UTC

We will be performing network maintenance at SG-SIN-2 (Singapore 2) on October 15th from 20:00 UTC to 00:00 UTC (October 16th). During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Posted on Sep 10, 2025 - 21:58 UTC

Scheduled Network Maintenance - US-SEA (Seattle) Oct 17, 2025 10:00-14:00 UTC

We will be performing network maintenance at US-SEA (Seattle) on October 17th from 10:00 UTC to 14:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Posted on Sep 10, 2025 - 22:00 UTC

Scheduled Network Maintenance - GB-LON (London 2) Oct 20, 2025 02:00-06:00 UTC

We will be performing network maintenance at GB-LON (London 2) on October 20th from 02:00 UTC to 06:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Posted on Sep 10, 2025 - 22:02 UTC

Maintenance for Linode Cloud Manager, API, and CLI Nov 5, 2025 03:00-05:00 UTC

The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 03:00 UTC and 05:00 UTC on November 5, 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, 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 Sep 11, 2025 - 19:18 UTC
Oct 8, 2025

Unresolved incident: Service Issue - Cloud Manager and API.

Oct 7, 2025
Service Issue - NodeBalancers Widespread
Resolved - We haven’t observed any additional issues with the NodeBalancer service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Oct 7, 23:41 UTC
Monitoring - Starting at 16:07 UTC on October 7th, 2025, our team became aware of a widespread issue affecting our NodeBalancer service. During this period of time, users may have experienced nodebalancer provisioning issues.
We can confirm that we have been able to correct the issues affecting the NodeBalancer service at approximately 20:10 UTC on October 7th, 2025. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a ticket with our Support Team.
Oct 7, 22:26 UTC
Scheduled Network Maintenance - DE-FRA-2 (Frankfurt 2)
Completed - The scheduled maintenance has been completed.
Oct 7, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 7, 03:00 UTC
Scheduled - We will be performing network maintenance at DE-FRA-2 (Frankfurt 2) on October 7th from 03:00 UTC to 07:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Sep 10, 21:51 UTC
Oct 6, 2025

No incidents reported.

Oct 5, 2025

No incidents reported.

Oct 4, 2025

No incidents reported.

Oct 3, 2025

No incidents reported.

Oct 2, 2025
Scheduled Network Maintenance - US-MIA (Miami)
Completed - The scheduled maintenance has been completed.
Oct 2, 13:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 2, 09:00 UTC
Scheduled - We will be performing network maintenance at US-MIA (Miami) on October 2nd from 09:00 UTC to 13:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Sep 10, 21:48 UTC
Emerging Service Issue - Cloud Manager and API
Resolved - We have mitigated the issues impacting the Cloud Manager and API services. If you continue to experience problems, please open a Support ticket for assistance.
Oct 2, 11:36 UTC
Investigating - Our team is investigating an additional emerging service issue affecting Cloud Manager and API in all regions. We will share additional updates as we have more information.
Oct 2, 10:45 UTC
Maintenance for Linode Cloud Manager, API, and CLI
Completed - The scheduled maintenance has been completed.
Oct 2, 04:21 UTC
Update - Scheduled maintenance is currently in progress and will be extended till 5:00 UTC.
Oct 2, 03:54 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 2, 02:00 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 04:00 UTC on October 2, 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, 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.
Sep 11, 19:20 UTC
Oct 1, 2025
Scheduled Network Maintenance - IN-BOM-2 (Mumbai 2)
Completed - The scheduled maintenance has been completed.
Oct 1, 06:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 1, 02:00 UTC
Scheduled - We will be performing network maintenance at IN-BOM-2 (Mumbai 2) on October 1st from 02:00 UTC to 06:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Sep 10, 21:46 UTC
Sep 30, 2025
Network Maintenance - Washington (US-IAD)
Completed - The scheduled maintenance has been completed.
Sep 30, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 30, 04:00 UTC
Scheduled - On Tuesday, September 30th at approximately 04:00 UTC to 10:00 UTC, we will be performing maintenance on the border routers in our Washington (US-IAD) region to complete an upgrade. The benefit of this upgrade is that it will help reduce bottlenecks and allow for greater capacity across the region. During this maintenance, there may be brief periods of packet loss and latency.
Sep 15, 18:40 UTC
Sep 29, 2025
Scheduled Network Maintenance - BR-GRU (Sao Paulo)
Completed - The scheduled maintenance has been completed.
Sep 29, 12:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 29, 08:00 UTC
Scheduled - We will be performing network maintenance at BR-GRU (Sao Paulo) on September 29th from 08:00 UTC to 12:00 UTC. During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Sep 10, 21:44 UTC
Sep 28, 2025
Connectivity Issue - India Regions (AP-WEST, IN-BOM-2, IN-MAA)
Postmortem - Read details
Sep 30, 16:39 UTC
Resolved - We haven’t observed any additional connectivity issues in our IN-MAA, AP-West, and IN-BOM-2 data centers, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Sep 28, 01:06 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.
Sep 27, 16:56 UTC
Identified - We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.
Sep 27, 14:27 UTC
Monitoring - Our team investigated an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data centers. The issue started at 11:00 UTC on September 27, 2025, and was mitigated at 12:19 UTC on September 27, 2025. During this time, users may have 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. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.
Sep 27, 14:03 UTC
Sep 27, 2025
Sep 26, 2025
Scheduled Longview Maintenance
Completed - The scheduled maintenance has been completed.
Sep 26, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 26, 04:30 UTC
Scheduled - We will be performing scheduled maintenance on our Longview service, starting at 04:30 UTC on September 26th. The maintenance period is expected to last 4 hours ending 08:30 UTC, September 26th. During this period, graphs will operate in read-only mode and new updates to the graphs will be temporarily unavailable during the downtime.
Sep 19, 07:49 UTC
Scheduled Network Maintenance - JP-OSA (Osaka)
Completed - The scheduled maintenance has been completed.
Sep 26, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 25, 20:00 UTC
Scheduled - We will be performing network maintenance at JP-OSA (Osaka) on September 25th from 20:00 UTC to 00:00 UTC (September 26th). During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Sep 10, 21:41 UTC
Sep 25, 2025
Service Issue - NodeBalancers (US-ORD, US-LAX, EU-WEST, FR-PAR, JP-OSA)
Resolved - We haven’t observed any additional issues with the NodeBalancer service in US‑ORD, US‑LAX, EU‑WEST, FR‑PAR, or JP‑OSA, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Sep 25, 18:08 UTC
Update - We are continuing to work on a fix for this issue. Most customers remain unaffected, but if you do encounter any problems with NodeBalancers, please open a ticket with our Support Team.
Sep 24, 16:10 UTC
Identified - Our team has identified the issue affecting the NodeBalancer service in our US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Sep 23, 20:10 UTC
Investigating - Our team is investigating an issue affecting the NodeBalancer service in the US-ORD, US-LAX, EU-WEST, FR-PAR, and JP-OSA regions. Some users in these regions may experience NodeBalancer service degradation, including performance issues. At this time, the number of customers impacted appears to be limited, but we are closely monitoring the situation as there is some risk of broader impact. We will share additional updates as we have more information.
Sep 23, 15:36 UTC
Service Issue - Linode Cloud Manager, API, and CLI - All Regions
Postmortem - Read details
Sep 25, 17:14 UTC
Resolved - We haven't observed any additional issues with the Cloud Manager, API or CLI, 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.
Sep 25, 08:59 UTC
Monitoring - At this time we have been able to correct the issue affecting the Cloud Manager, API and CLI. 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.
Sep 24, 11:32 UTC
Identified - Our team has identified the issue affecting the Cloud Manager, API and CLI. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Sep 24, 10:40 UTC
Investigating - Our team is investigating a service issue that affects the Cloud Manager (https://cloud.linode.com/) and API. During that time, some users may experience issues when attempting to access these systems. We will share additional updates as we have more information.
Sep 24, 09:47 UTC
Scheduled Longview Maintenance
Completed - The scheduled maintenance has been completed.
Sep 25, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 25, 04:30 UTC
Scheduled - We will be performing scheduled maintenance on our Longview service, starting at 04:30 UTC on September 25th. The maintenance period is expected to last 4 hours ending 08:30 UTC, September 25th. During this period, graphs will operate in read-only mode and new updates to the graphs will be temporarily unavailable during the downtime.
Sep 19, 07:47 UTC
Scheduled Network Maintenance - JP-TYO-3 (Tokyo 3)
Completed - The scheduled maintenance has been completed.
Sep 25, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 24, 20:00 UTC
Scheduled - We will be performing network maintenance at JP-TYO-3 (Tokyo 3) on September 24th from 20:00 UTC to 00:00 UTC (September 25th). During this window, changes will be made to enhance routing stability, improve convergence performance, and enable additional support for advanced routing features. Individuals may experience short-lived packet loss or latency spikes while maintenance occurs.
Sep 10, 21:36 UTC
Sep 24, 2025
Scheduled Longview Maintenance
Completed - The scheduled maintenance has been completed.
Sep 24, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 24, 04:30 UTC
Scheduled - We will be performing scheduled maintenance on our Longview service, starting at 04:30 UTC on September 24th. The maintenance period is expected to last 4 hours ending 08:30 UTC, September 24th. During this period, graphs will operate in read-only mode and new updates to the graphs will be temporarily unavailable during the downtime.
Sep 19, 07:46 UTC
Service Issue - Linode Kubernetes Engine - US-Southeast (Atlanta)
Postmortem - Read details
Sep 24, 17:18 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.
Sep 24, 08:05 UTC
Monitoring - At this time we have been able to correct the issues affecting the LKE 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.
Sep 24, 07:23 UTC
Identified - We have determined the root cause of this issue and are working on implementing a fix. We will provide an update as soon as the solution is in place.
Sep 24, 06:28 UTC
Update - Our subject matter experts are continuing to investigate this issue. We will provide the next update as we make progress.
Sep 24, 05:42 UTC
Investigating - Our team is investigating an emerging service issue affecting LKE services in Atlanta. We will share additional updates as we have more information.
Sep 24, 04:31 UTC
Connectivity Issue - India Regions (AP-WEST, IN-BOM-2, IN-MAA)
Postmortem - Read details
Sep 24, 07:18 UTC
Resolved - We haven’t observed any additional connectivity issues in our IN-MAA, AP-West, IN-BOM-2 data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Sep 24, 07:09 UTC
Monitoring - Connectivity to our India Compute regions (IN-MAA, AP-West, IN-BOM-2) has improved. Since September 14, 2025, we have not observed the recurring packet loss that previously affected traffic to and from EU & US locations during India peak business hours. Our network providers reported that backbone capacity in Asia has been stabilized and operations are largely restored.
At this time, customers may still notice slightly higher latency when connecting to Europe and the U.S. East Coast. Providers have indicated that this condition may persist for the next couple of weeks. We will continue to monitor the services.
Sep 19, 04:22 UTC
Update - We are continuing to experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. Between approximately 17:02 UTC and 18:20 UTC on September 12, 2025, we experienced an increase in intermittent connection failures and latency in all the services deployed in IN-MAA. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.
Sep 12, 18:35 UTC
Update - Linodes in our IN-MAA, AP-West, and IN-BOM data centers are experiencing increased network congestion and latency due to multiple faults in the undersea cables that are part of the optimal routes out of the data centers. There is currently no estimated time-to-resolution available from the undersea cable operators. We continue to work on mitigating customer impact with our third-party network providers and will share additional updates as soon as they become available.
Sep 7, 18:22 UTC
Identified - We are continuing experience connection issues affecting our IN-MAA, AP-West, and IN-BOM data centers. During this time users may experience intermittent connection issues and network slowness for all services deployed in these data centers. We are currently working on mitigating customer impact with our 3rd party network providers and will share additional updates as soon as they are available.
Sep 6, 12:20 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 data center. We will continue to monitor for further connection issues. If you are still experiencing issues, please open a Support ticket for assistance.
Sep 6, 10:16 UTC
Investigating - Our team is investigating an issue affecting connectivity in our IN-MAA, AP-West and IN-BOM-2 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.
Sep 6, 02:53 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity in our AP-West and IN-BOM-2 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.
Sep 6, 01:56 UTC
Investigating - Our team is investigating an issue affecting connectivity in our Mumbai, IN 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.
Sep 5, 23:41 UTC
← Incident History Powered by Atlassian Statuspage