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

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 (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 - 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

Scheduled Emergency Network Maintenance - US-East (Newark) Nov 4, 2025 07:00-11:00 UTC

We will be performing a scheduled network maintenance in our US-East (Newark) data center from 07:00 (UTC) until 11:00 (UTC) on Tuesday, November 4, 2025. While we do not expect any downtime, a brief period of increased latency or packet loss may occur.
Posted on Oct 16, 2025 - 16:26 UTC

Maintenance for Linode Cloud Manager, API, and CLI Nov 12, 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 12, 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 17, 2025

No incidents reported today.

Oct 16, 2025
Service Issue - Cloud Manager and API
Resolved - We haven't observed any additional issues with the Cloud Manager or API, 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.
Oct 16, 16:06 UTC
Update - We have implemented a fix for this issue as of October 7, 2025. Based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000cRKGoCAO

We will continue to monitor to ensure that the impact has been fully mitigated.
Oct 15, 17:12 UTC
Update - We have not seen issues since 7 October 2025 and are continuing to monitor further. If you are still experiencing issues, please open a Support ticket for assistance.
Oct 15, 09:23 UTC
Update - We are continuing to monitor for any further issues.
Oct 8, 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 2, 08:00 UTC
Update - We are continuing to investigate this issue.
Oct 2, 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 1, 22:05 UTC
Scheduled Network Maintenance - SG-SIN-2 (Singapore 2)
Completed - The scheduled maintenance has been completed.
Oct 16, 00:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 20:00 UTC
Scheduled - 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.
Sep 10, 21:58 UTC
Oct 15, 2025
Service Issue - Object Storage
Resolved - We haven’t observed any additional issues with the Object Storage service in any of the impacted regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Oct 15, 23:03 UTC
Monitoring - At this time we have been able to correct the issues affecting the Object Storage service. The impacted regions and their impact windows are listed below. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Location and time, in UTC, all dated 2025-10-15:
Chicago (US-ORD): 10:46-10:52
London (GB-LON): 10:52-10:59
Washington, DC (US-IAD): 12:26-13:54
Seattle (US-SEA): 13:14-13:23
Singapore 2 (SG-SIN-2): 14:00-14:09
Melbourne (AU-MEL): 14:57-15:04
Tokyo 3 (JP-TYO-3): 12:34-12:42
Oct 15, 19:42 UTC
Update - We have narrowed down the impacted regions to be E2 and E3 endpoint regions. Our list below has been updated to reflect this.
Oct 15, 18:20 UTC
Update - We are continuing to investigate this issue.
Oct 15, 18:10 UTC
Investigating - Our team is investigating an emerging service issue affecting Object Storage in multiple locations. We will share additional updates as we have more information.
Oct 15, 18:00 UTC
Service Issue - Networking - IAD3
Resolved - This incident has been resolved.
Oct 15, 17:53 UTC
Update - We are continuing to monitor for any further issues.
Oct 15, 00:08 UTC
Monitoring - At 18:41 UTC on October 14th, 2025 we have been able to correct the issues affecting connectivity in our Washington (IAD3) 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.
Oct 14, 18:53 UTC
Update - We are continuing to investigate this issue and we will share additional updates as we have more information.
Oct 14, 18:25 UTC
Investigating - Our team is investigating an emerging service issue affecting Networking in IAD3. We will share additional updates as we have more information.
Oct 14, 17:24 UTC
Oct 14, 2025
Network Maintenance - Washington (US-IAD)
Completed - The scheduled maintenance has been completed.
Oct 14, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 14, 04:00 UTC
Scheduled - 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.
Sep 29, 18:22 UTC
Oct 13, 2025
Scheduled Network Maintenance - ID-CGK (Jakarta)
Completed - The scheduled maintenance has been completed.
Oct 13, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 13, 19:00 UTC
Scheduled - 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.
Sep 10, 21:56 UTC
Oct 12, 2025

No incidents reported.

Oct 11, 2025

No incidents reported.

Oct 10, 2025

No incidents reported.

Oct 9, 2025
Scheduled Network Maintenance - NL-AMS (Amsterdam)
Completed - The scheduled maintenance has been completed.
Oct 9, 05:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 9, 01:00 UTC
Scheduled - 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.
Sep 10, 21:54 UTC
Oct 8, 2025
Oct 7, 2025
Service Issue - NodeBalancers Widespread
Postmortem - Read details
Oct 15, 00:32 UTC
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.

← Incident History Powered by Atlassian Statuspage