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

Linode Status

← Current Status
Service Issue - GPU and VPU Booting issues
Update - We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Apr 15, 2026 - 15:12 UTC
Update - We are currently deploying a fix for this issue in phases, which will take several weeks to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Apr 06, 2026 - 13:39 UTC
Update - We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Mar 19, 2026 - 20:13 UTC
Update - We are currently deploying a fix for this issue in phases, which will take several days to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Feb 26, 2026 - 15:42 UTC
Update - We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
Feb 19, 2026 - 16:41 UTC
Update - We are continuing to test the fix before initiating the rollout. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
Feb 03, 2026 - 15:34 UTC
Update - We have successfully identified a solution to address the issue at hand. We are currently in the testing phase prior to initiating the rollout of the fix. Further updates regarding the status of the mitigation efforts will be provided as progress is made.
Jan 05, 2026 - 19:30 UTC
Update - We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
Jan 05, 2026 - 17:16 UTC
Update - We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
Dec 17, 2025 - 13:40 UTC
Update - We are continuing to work on a fix for this issue, and we will provide an update as soon as the solution is in place.
Dec 04, 2025 - 20:51 UTC
Identified - Our team has identified the issue affecting booting up GPU and VPU plans. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Dec 03, 2025 - 16:48 UTC
Investigating - Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.
Dec 03, 2025 - 15:15 UTC
Linode.com Operational
Linode Manager and API Operational
Hosted DNS Service Operational
Longview Operational
Managed Databases Operational
ACLP Logs 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
FR-PAR-2 (Paris 2) Operational
Backups Operational
US-East (Newark) Backups Operational
US-Central (Dallas) Backups Operational
US-West (Fremont) Backups Operational
US-Southeast (Atlanta) Backups Operational
US-IAD (Washington) Backups Operational
US-ORD (Chicago) Backups Operational
CA-Central (Toronto) Backups Operational
EU-West (London) Backups Operational
EU-Central (Frankfurt) Backups Operational
FR-PAR (Paris) Backups Operational
AP-South (Singapore) Backups Operational
AP-Northeast-2 (Tokyo 2) Backups Operational
AP-West (Mumbai) Backups Operational
AP-Southeast (Sydney) Backups Operational
SE-STO (Stockholm) Backups Operational
US-SEA (Seattle) Backups Operational
JP-OSA (Osaka) Backups Operational
IN-MAA (Chennai) Backups Operational
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 (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

Maintenance for Linode Cloud Manager, API, and CLI Apr 18, 2026 18:00-19:30 UTC

The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 1800 UTC to 1930 (UTC) on April 18, 2026.

During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services, Kubernetes autoscaling, or management of PVCs and Nodebalancers. Interruptions expected during this window should be brief and only expected to last a few minutes, 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 Mar 10, 2026 - 21:14 UTC

Maintenance for Linode Cloud Manager, API, and CLI Apr 19, 2026 18:00-19:30 UTC

The Linode Cloud Manager, API, and CLI will be undergoing scheduled maintenance between 1800 UTC to 1930 (UTC) on April 19, 2026.

During this window, running Linodes and related services will not be disrupted, but there may be brief periods of increased latency of responses or unavailability of the Linode Cloud Manager, API, and CLI.

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 may 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 may 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 brief periods 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:
For brief periods during the maintenance window, current Linode customers may not be able to log in to the Cloud Manager, interact with the API, or perform any administrative or management functions. This includes actions such as create, remove, boot, migrate, back up, shut down, etc across all Linode services, Kubernetes autoscaling, or management of PVCs and Nodebalancers. Interruptions expected during this window should be brief and only expected to last a few minutes, 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 Mar 10, 2026 - 21:16 UTC

Scheduled Maintenance – Cloud Manager, API, Cloud IAM and CLI Apr 22, 2026 04:00-05:30 UTC

Update - We will be undergoing scheduled maintenance during this time.
Mar 19, 2026 - 03:21 UTC
Update - We will be undergoing scheduled maintenance during this time.
Mar 19, 2026 - 03:20 UTC
Scheduled - Scheduled Maintenance — Cloud Manager, API, Cloud IAM and CLI

April 22, 2026
04:00 UTC – 05:30 UTC

The Linode Cloud Manager, API, Cloud IAM and CLI will be unavailable during this scheduled maintenance window.

Running Linodes and existing workloads will continue operating normally during this time. However, customers will not be able to access the Cloud Manager, interact with the API, or perform account or infrastructure management actions until maintenance is complete.

This includes actions such as creating or modifying resources, managing configurations, or accessing Support tickets through the Cloud Manager.

During this maintenance window:

- Kubernetes cluster workloads will continue running normally. However, actions that require the Linode API such as creating new clusters or scaling operations will not be available until maintenance is complete.

- New account creation and account authentication will be temporarily unavailable while the Cloud Manager is offline.

Customers who require assistance from Linode Support during this window may contact our Support team by phone:

United States: 855-454-6633
International: +1-609-380-7100

Please note that while phone support will be available, Support teams will not be able to assist with actions that require Cloud Manager or API access until maintenance is complete — this includes responding to Support tickets.

We recommend completing any time-sensitive administrative tasks before the maintenance window begins.

We will provide an update on this page once maintenance has been completed and full access to all services has been restored.

Thank you for your patience and understanding.
Mar 17, 2026 - 21:58 UTC
Apr 18, 2026

No incidents reported today.

Apr 17, 2026
Linode Kubernetes Engine Standard and Enterprise provisioning failures in all regions
Resolved - We haven’t observed any additional issues with the LKE and LKE-E services, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Apr 17, 13:30 UTC
Monitoring - As of 16:27 UTC on April 16, 2026 we have corrected the issues affecting the LKE service. The issue was caused by an expired certificate, which has been updated. We will be monitoring this to ensure that it remains stable.

If you continue to experience problems, please open a Support ticket for assistance.
Apr 16, 16:53 UTC
Update - As of 15:53 UTC on April 16, 2026 we are starting to see nodes successfully provisioning, however the service is not fully back up yet. Some customers may remain impacted at this time. We are working to stabilize the service, and will provide another update within the next 30 minutes.

Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 16:09 UTC
Update - Our team continues to work on implementing a fix for the issue affecting the Linode Kubernetes Engine. We will continue to provide updates until a solution is in place.

Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 15:40 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.

Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 15:10 UTC
Update - Our team continues to investigate the issue affecting the Linode Kubernetes Engine (LKE). We will share additional updates as we have more information.

Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 14:41 UTC
Update - Our team continues to investigate the issue with the Linode Kubernetes Engine. Affected customers may be unable to deploy new clusters or add new nodes to a cluster. We will share additional updates as we have more information.

Customers can find more information on the Akamai Community at https://community.akamai.com/customers/s/feed/0D5a7000013vgM6CAI
Apr 16, 14:12 UTC
Investigating - Our team is investigating an emerging service issue affecting Linode Kubernetes Engine Standard and Enterprise in all regions. We will share additional updates as we have more information.
Apr 16, 13:20 UTC
Apr 16, 2026
Service Issue - Dedicated CPU - Several Regions
Postmortem - Read details
Apr 17, 17:03 UTC
Resolved - We haven't observed any additional issues with the Dedicated CPU offering, 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 16, 19:32 UTC
Update - We have identified a fix for the issue affecting the Dedicated CPU offering and are currently testing it. We expect to include the fix in the next software release that is expected to happen by the end of May.
Our investigation shows that approximately 0.2% of hosts were impacted by this issue. In the meantime, a workaround is available by contacting support.
We will provide additional updates as we approach the deployment date.
Apr 15, 22:40 UTC
Identified - Our team has identified the issue affecting the Dedicated CPU offering. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 14, 20:45 UTC
Investigating - Our team is investigating a service issue that affects the Dedicated CPU offering. Some users may experience failed Linode boots, errors related to insufficient resource allocation, unsuccessful migrations of Dedicated CPU plans or scaling of LKE clusters, and difficulty deploying or scaling workloads that require Dedicated CPU resources. We will share additional updates as we have more information.
Apr 14, 18:33 UTC
Apr 15, 2026
Service Issue - Cloud Manager and API
Postmortem - Read details
Apr 17, 19:41 UTC
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.
Apr 15, 20:21 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 15, 18:35 UTC
Update - We are continuing to implement a fix, and we will provide an update as soon as the solution is in place.
Apr 15, 18:28 UTC
Identified - Our team has identified the issue affecting the Cloud Manager and API. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place. During this time, customers may be unable to create new Linodes, make changes to Cloud Firewalls, initiate migrations or resize operations. LKE autoscaling may also be delayed during this time.
Apr 15, 16:57 UTC
Apr 14, 2026
Scheduled maintenance- Cloud Manager Analytics
Completed - The scheduled maintenance has been completed.
Apr 14, 07:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 14, 05:30 UTC
Scheduled - We will be performing scheduled maintenance on our servers responsible for Cloud Manager Analytics in Dallas starting at 05:30 UTC on April 14th, 2026. The maintenance period is expected to last 2 hours ending 07:30 UTC, April 14th, 2026. While existing graphs will continue to be displayed normally, please be aware that a slight delay in graph updates may be observed during the process.
Apr 9, 08:22 UTC
Apr 13, 2026
Maintenance for Linode Support Ticketing System
Completed - The scheduled maintenance has been completed.
Apr 13, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 13, 14:00 UTC
Scheduled - On Monday, April 13, 2026, starting at 2:00 PM UTC, We will be performing planned maintenance on the Linode Support Ticketing System.

There is no expected downtime.
Apr 13, 14:00 UTC
Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026
Service Issue - Networking in US-IAD (Washington)
Postmortem - Read details
Apr 13, 04:51 UTC
Resolved - We have successfully resolved the networking issues in the US-IAD (Washington) data center. The cause was identified as a specific compute host that generated abnormal network traffic upon being powered on, which impacted the local management network and a subset of customer connectivity. Our engineering team has isolated the hardware responsible, and network stability was restored immediately.
All management services are fully operational, and the backlog of pending host jobs has been completely processed. We will continue to monitor the region to ensure ongoing stability. Please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.
Apr 10, 02:31 UTC
Update - We are continuing to investigate the issue. We will provide the next update as we make progress.
Apr 10, 01:04 UTC
Update - Our team continues to investigate the issue affecting networking in US-IAD (Washington) 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 within the next 60 minutes.
Apr 10, 00:27 UTC
Investigating - Our team is investigating an emerging service issue affecting networking in US-IAD (Washington). We will share additional updates as we have more information.
Apr 9, 23:32 UTC
Apr 9, 2026
Apr 8, 2026
Scheduled Longview Maintenance - US-Central (Dallas)
Completed - The scheduled maintenance has been completed.
Apr 8, 08:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 8, 05:30 UTC
Scheduled - We will be performing scheduled maintenance on our Longview service in Dallas starting at 05:30 UTC on April 8th, 2026. The maintenance period is expected to last 2 hours ending 07:30 UTC, April 8th, 2026. While existing graphs will continue to be displayed normally, please be aware that any new data updates to the graphs may be temporarily unavailable during this timeframe. Full functionality will resume following the completion of the maintenance.
Apr 2, 08:59 UTC
Emerging Service Issue - Network - London 2(gb-lon)
Resolved - We haven’t observed any additional connectivity issues and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Apr 8, 06:32 UTC
Monitoring - We've determined that the impact of the issue caused by an upstream AS has been mitigated. We continue to monitor the situation until we recieve further confirmation of the resolution.
Apr 7, 10:17 UTC
Investigating - Our team is investigating an emerging service issue affecting connectivity to our Linode infrastructure in the London 2(gb-ion) region likely caused due to a upstream AS. We will continue to share more details as we verify this.
Apr 7, 09:02 UTC
Apr 7, 2026
Network Maintenance- US-IAD(Washington)
Completed - The scheduled maintenance has been completed.
Apr 7, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 7, 04:00 UTC
Scheduled - We will be performing a network maintenance in our IAD (Washington DC) data center from 04:00 (UTC) until 10:00 (UTC) on Tuesday, April 7th, 2026. While we do not expect any downtime, a brief period of increased latency or packet loss may occur. If you have questions surrounding this Scheduled Maintenance please open a Support ticket for assistance.
Mar 26, 18:15 UTC
Emerging Service Issue - Object Storage - us-east-1
Resolved - This incident has been resolved.
Apr 7, 01:39 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 7, 01:13 UTC
Investigating - Our team is investigating an emerging service issue affecting Object Storage in us-east-1. We will share additional updates as we have more information.
Apr 7, 00:50 UTC
Apr 6, 2026
Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage