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

Linode Status

← Current Status
Service Issue - LAX
Update - We identified a brief period of impact to network traffic connectivity in our US-LAX (Los Angeles) data center between 19:55 - 19:58 UTC on April 25, 2025. We are continuing to monitor this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Apr 25, 2025 - 20:25 UTC
Update - We haven’t observed any additional connectivity issues since 17:55 UTC on April 24, 2025. We are continuing to monitor this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Apr 25, 2025 - 19:21 UTC
Monitoring - We identified a brief period of impact to network traffic connectivity in our US-LAX (Los Angeles) DataCenter between 17:32 - 17:55 UTC on April 24, 2025. We are continuing to monitor this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Apr 24, 2025 - 21:25 UTC
Update - We are continuing to investigate this issue.
Apr 24, 2025 - 17:57 UTC
Investigating - Our team is investigating an emerging service issue affecting all services in the LAX. We will share additional updates as we have more information.
Apr 24, 2025 - 17:57 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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Maintenance for Cloud Manager, API, and CLI May 14, 2025 02:00-05:00 UTC

Update - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on May 14, 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.
Apr 15, 2025 - 20:06 UTC
Scheduled - The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 02:00 UTC and 05:00 UTC on May 14, 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.
Apr 04, 2025 - 16:48 UTC
Apr 26, 2025

No incidents reported today.

Apr 25, 2025
Scheduled Network Maintenance - JP-TYO-3 (Tokyo 3)
Completed - We are canceling the maintenance scheduled in our JP-TYO-3 (Tokyo 3) data center for 1 May 2025, 23:00 UTC that was expected to be completed on 2 May 2025, 03:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 25, 14:21 UTC
Scheduled - We will be performing network maintenance in our JP-TYO-3 (Tokyo 3) data center from 23:00 UTC on May 1, 2025 to 03:00 UTC on May 2, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 14, 22:04 UTC
Scheduled Network Maintenance - ES-MAD (Madrid)
Completed - We are canceling the maintenance scheduled in our ES-MAD (Madrid) data center for 30 April 2025, 05:00 UTC that was expected to be completed on 30 April 2025, 09:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 25, 14:20 UTC
Scheduled - We will be performing network maintenance in our ES-MAD (Madrid) data center between 05:00 UTC and 09:00 UTC on April 30, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 14, 22:02 UTC
Scheduled Network Maintenance - JP-OSA (Osaka)
Completed - We are canceling the maintenance scheduled in our JP-OSA (Osaka) data center for 29 April 2025, 22:00 UTC that was expected to be completed on 30 April 2025, 02:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 25, 14:20 UTC
Scheduled - We will be performing network maintenance in our JP-OSA (Osaka) data center from 22:00 UTC on April 29, 2025 to 02:00 UTC on April 30, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 14, 22:01 UTC
Apr 24, 2025
Emergency Network Maintenance - AP-West (Mumbai)
Completed - The scheduled maintenance has been completed.
Apr 24, 21:05 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 24, 17:05 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-West (Mumbai) data center beginning 24 April 2025 17:00 (UTC) until 24 April 2025 21:00 (UTC). During this time, users with resources in the AP-West (Mumbai) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Apr 24, 17:04 UTC
Emergency Network Maintenance - AP-South (Singapore)
Completed - The scheduled maintenance has been completed.
Apr 24, 17:22 UTC
Verifying - Verification is currently underway for the maintenance items.
Apr 24, 17:12 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 24, 17:00 UTC
Scheduled - We will be performing an emergency network maintenance in our AP-South (Singapore) data center beginning 24 April 2025 17:00 (UTC) until 24 April 2025 21:00 (UTC). During this time, users with resources in the AP-South (Singapore) region may experience intermittent issues when attempting to take actions like creating, updating, and deleting resources within this region
Apr 24, 12:36 UTC
Scheduled Network Maintenance - JP-TYO-3 (Tokyo 3)
Completed - The scheduled maintenance has been completed.
Apr 24, 02:00 UTC
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Apr 24, 01:37 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 24, 01:00 UTC
Scheduled - We will be performing network maintenance in our JP-TYO-3 (Tokyo 3) data center from 01:00 UTC to 05:00 UTC on April 24, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 10, 15:23 UTC
Apr 23, 2025
Connectivity Issue - Asia Data Centers
Resolved - We haven’t observed any additional connectivity issues in our Asia region data centers and will now consider this incident resolved. The third party has addressed the underlying issues, resulting in improved performance and stability. If you continue to experience problems, please open a Support ticket for assistance.
Apr 23, 19:42 UTC
Update - The third-party continues working on a fix for this issue, and due to the complexity of this problem, it will take longer to mitigate it completely. In the meantime, we continue monitoring our systems. If you are still experiencing issues, please open a Support ticket for assistance.
Feb 25, 19:44 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity from our Asia to Europe Data Centers. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Jan 27, 10:16 UTC
Identified - Our team has identified a third-party issue affecting connectivity from our Asia to Europe Data Centers between ~02:10 to ~14:58 UTC on January 25, 2025. During this time, users may have experienced latency and potential congestion on some providers between Asia and Europe. 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.
Jan 25, 16:49 UTC
Emerging Service Issue - Network Connectivity - US - Central (Dallas)
Resolved - The root cause was traced back to a congestion on a third-party transit provider. We haven’t observed any additional connectivity issues towards our US - Central (Dallas) region, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Apr 23, 13:05 UTC
Monitoring - Starting approximately 23:00 UTC on 22 April 2025, we observed intermittent networking issues towards our US - Central (Dallas) location from various geolocations. We have traced these issues down to a 3rd party transit provider and re-routed the traffic to Dallas through alternate transit providers. We have not observed any more packet loss since 02:30 UTC on 23 April 2025 and are continuing to monitor these routes. If you continue to experience problems, please open a Support ticket for assistance.
Apr 23, 03:00 UTC
Investigating - Our team is investigating an emerging service issue affecting network connectivity in US Central (Dallas). We will share additional updates as we have more information.
Apr 23, 02:32 UTC
Apr 22, 2025

No incidents reported.

Apr 21, 2025

No incidents reported.

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025
Scheduled Network Maintenance - SE-STO (Stockholm)
Completed - We are canceling the maintenance scheduled in our SE-STO (Stockholm) data center for 29 April 2025, 01:00 UTC that was expected to be completed on 29 April 2025, 05:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 18, 17:22 UTC
Scheduled - We will be performing network maintenance in our SE-STO (Stockholm) data center between 01:00 UTC and 05:00 UTC on April 29, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 14, 21:58 UTC
Scheduled Network Maintenance - IT-MIL (Milan)
Completed - We are canceling the maintenance scheduled in our IT-MIL (Milan) data center for 24 April 2025, 04:00 UTC that was expected to be completed on 24 April 2025, 08:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 18, 17:22 UTC
Scheduled - We will be performing network maintenance in our IT-MIL (Milan) data center between 04:00 UTC and 08:00 UTC on April 24, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 8, 12:17 UTC
Scheduled Network Maintenance - IN-MAA (Chennai)
Completed - We are canceling the maintenance scheduled in our IN-MAA (Chennai) data center for 23 April 2025, 18:30 UTC that was expected to be completed on 23 April 2025, 22:30 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 18, 17:21 UTC
Update - We are updating the schedule for the maintenance to a slightly earlier timeframe. We will now be performing network maintenance in our IN-MAA (Chennai) data center between 18:30 UTC and 22:30 UTC on April 23, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 10, 12:04 UTC
Scheduled - Updated Schedule: We will be performing network maintenance in our IN-MAA (Chennai) data center between 18:30 UTC and 22:30 UTC on April 23, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 8, 12:16 UTC
Scheduled Network Maintenance - US-LAX (Los Angeles)
Completed - We are canceling the maintenance scheduled in our US-LAX (Los Angeles) data center for 23 April 2025, 00:00 UTC that was expected to be completed on 23 April 2025, 04:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 18, 17:19 UTC
Scheduled - We will be performing network maintenance in our US-LAX (Los Angeles) data center between 00:00 UTC and 04:00 UTC on April 23, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 8, 12:15 UTC
Scheduled Network Maintenance - US-SEA (Seattle)
Completed - We are canceling the maintenance scheduled in our US-SEA (Seattle) data center for 21 April 2025, 10:00 UTC that was expected to be completed on 21 April 2025, 14:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 18, 17:19 UTC
Scheduled - We will be performing network maintenance in our US-SEA (Seattle) data center between 10:00 UTC and 14:00 UTC on April 21, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 8, 12:13 UTC
Apr 17, 2025
Scheduled Network Maintenance - AU-MEL (Melbourne)
Completed - We are canceling the maintenance scheduled in our AU-MEL (Melbourne) data center for 18 April 2025, 02:00 UTC that was expected to be completed on 18 April 2025, 06:00 UTC. It will be rescheduled to a later date that will be communicated in advance.
Apr 17, 21:16 UTC
Scheduled - We will be performing network maintenance in our AU-MEL (Melbourne) data center between 02:00 UTC and 06:00 UTC on April 18, 2025. Although we do not anticipate any impact, during this time there may be brief network connectivity disruptions.
Apr 3, 23:27 UTC
Emerging Service Issue - Connectivity Across Multiple Regions
Postmortem - Read details
Apr 18, 00:15 UTC
Resolved - We haven’t observed any additional connectivity issues in our multiple data centers, and will now consider this incident resolved. During the impact window, we did not experience issues with Cloud Manager and API. If you continue to experience problems, please open a Support ticket for assistance.
Apr 17, 14:44 UTC
Monitoring - At this time we have been able to correct the issue affecting the Cloud Manager and API. 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.
Apr 17, 03:31 UTC
Update - We are continuing to work on a resolution for this issue. Subsequent updates around mitigation status will be posted as progress is made.
Apr 17, 01:02 UTC
Identified - After performing mitigation actions we became aware the issue is still occurring; the issue is identified and a fix is being implemented.
Apr 16, 23:08 UTC
Monitoring - At this time we have been able to correct the issues affecting connectivity. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Apr 16, 22:39 UTC
Identified - We've identified a root cause and are applying a mitigation as quickly as possible. We'll continue to post updates as this incident develops.
Apr 16, 22:16 UTC
Update - We are working quickly on mitigating this issue. We will share additional updates as we have more information.
Apr 16, 21:25 UTC
Investigating - Our team is investigating an emerging service issue affecting connectivity in multiple regions. We will share additional updates as we have more information.
Apr 16, 20:35 UTC
Apr 16, 2025
Apr 15, 2025
Service Issue - Intermittent connection drops on LKE pod to pod traffic
Resolved - We haven't observed any additional issues with the Linode Kubernetes Engine (LKE), 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.
Apr 15, 00:35 UTC
Monitoring - At this time we have been able to correct the issue affecting the Linode Kubernetes Engine (LKE). 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.
Apr 14, 22:24 UTC
Update - We are continuing to investigate this issue and will provide additional updates as progress is made.
Apr 12, 00:35 UTC
Update - We are continuing to investigate this issue and will provide additional updates as progress is made.
Apr 11, 00:10 UTC
Update - We are continuing to investigate this issue and will provide additional updates as progress is made.
Apr 9, 23:45 UTC
Update - We are continuing to investigate this issue and will provide additional updates as progress is made.
Apr 9, 00:42 UTC
Update - We are continuing to investigate this issue and will provide additional updates as progress is made.
Apr 7, 22:56 UTC
Update - The investigation continues, at the time we have been able to confirm the issue is causing intermittent instances of 1-2 mins connection timeouts between pod to pod traffic. These timeouts have been identified in only 2 of our Data Centers with only few ocurrences and we continue to work to identify the cause. Due to the intermittent nature of the issue the investigation will take additional time and will provide additional updates as progress is made. Should you notice issues with symptoms that align to this, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email open a Support ticket for assistance.
Apr 4, 20:34 UTC
Update - We are continuing to investigate this issue and will provide additional updates as progress is made.
Apr 4, 19:34 UTC
Update - We are continuing to investigate this issue.
Apr 4, 17:14 UTC
Investigating - Our team is investigating an issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information.
Apr 4, 16:42 UTC
Apr 14, 2025
Apr 13, 2025

No incidents reported.

Apr 12, 2025
← Incident History Powered by Atlassian Statuspage