Linode Status

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.

Identified: Our team has identified and is investigating an emerging issue affecting the Cloud Manager and API, in which VPC endpoints are experiencing occasional degradation. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place

Monitoring: We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.

Monitoring: We will continue to monitor our systems for any further issues this weekend. If you are still experiencing problems, please open a support ticket for assistance.

Monitoring: We are continuing to monitor for any further issues. If you are still experiencing issues, please open a Support ticket for assistance.

Monitoring: At this time, we have been able to correct the issues affecting connectivity in our US-IAD (Washington) data center. We will be monitoring this to ensure that it remains stable. In the meantime, we will continue investigating the cause of the network issue experienced during the maintenance. If you are still experiencing issues, please open a Support ticket for assistance.

Identified: The work in the maintenance window caused unexpected network connectivity issues. We are currently working on identifying the cause of that impact as it was not expected. We continue to work on mitigating the issue and will provide more updates as they become available. If you are experiencing issues, please open a Support ticket for assistance.

Identified: We are continuing to work on a fix for this issue. Subsequent updates will be posted as progress is made.

Identified: Our team has identified the issue affecting connectivity in our US-IAD (Washington) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

Investigating: We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.

Investigating: We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.

Investigating: We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.

Investigating: Our team is investigating an issue affecting connectivity in our US-IAD (Washington) data center. During this time, users may experience intermittent connection timeouts and errors for all services deployed in this data center. Compute instances running on Premium instances are not impacted by this issue. We will share additional updates as we have more information.

Resolved: We haven’t observed any additional connectivity issues in our Mumbai data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Our team has identified the issue affecting connectivity in our Mumbai data center that started at approximately 15:20 UTC on January 16th, 2025. The issue was mitigated at approximately 17:40 UTC On January 16th, 2025. During this period, customers may have experienced host drops and delays in job processing. Our team will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.

Resolved: We haven’t observed any additional connectivity issues in our Chennai data center, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting connectivity in our Chennai data center. We will be monitoring this to ensure that it remains stable, and will provide another update when the monitoring period is complete. If you are still experiencing issues, please open a Support ticket for assistance.

Investigating: We are currently investigating an issue affecting connectivity in the Chennai data center. Traffic between Chennai and Dallas was also impacted from 18:34 UTC-20:05 UTC, however this has been mitigated. We will provide updates as they become available.

Monitoring: Our team has identified an issue affecting our Block Storage service in our US-ORD (Chicago), US-IAD (Washington, D.C.) and Los Angeles (LAX3) data centers between the following times:

• Chicago (ORD2): 21:57 UTC to 22:18 UTC
• Washington, D.C. (IAD3): 22:07 UTC to 22:20 UTC
• Los Angeles (LAX3): 21:32 UTC to 21:45 UTC During this time, users may have experienced slow or failed storage operations for their Block Storage Clients. We have been able to correct the issues and the service has resumed normal operations. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Our team has identified an issue affecting our Block Storage service in our US-ORD (Chicago), US-IAD (Washington, D.C.) and Los Angeles (LAX3) data centers between the following times:

• Chicago (ORD2): 21:57 UTC to 22:18 UTC
• Washington, D.C. (IAD3): 22:07 UTC to 22:20 UTC
• Los Angeles (LAX3): 21:32 UTC to 21:45 UTC During this time, users may have experienced slow or failed storage operations for their Block Storage Clients. We have been able to correct the issues and the service has resumed normal operations. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Our team has identified an issue affecting our Block Storage service in our US-ORD (Chicago), US-IAD (Washington, D.C.) and Los Angeles (LAX3) data centers between the following times:

• Chicago (ORD2): 21:57 UTC to 22:18 UTC
• Washington, D.C. (IAD3): 22:07 UTC to 22:20 UTC
• Los Angeles (LAX3): 21:32 UTC to 21:45 UTC During this time, users may have experienced slow or failed storage operations for their Block Storage Clients. We have been able to correct the issues and the service has resumed normal operations. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: At this time we have been able to correct the issues affecting the NodeBalancer service. 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.

Investigating: Our team is investigating an issue affecting the NodeBalancer service in our US-ORD data center. During this time, users may experience issues creating NodeBalancers in the US-ORD data center. We will share additional updates as we have more information.

Postmortem: On January 9, 2025, starting at approximately 21:18 UTC, customers using the US-ORD-1 cluster in Chicago experienced intermittent latency with cluster operations. Telemetry from our canary monitoring detected that operations in this data center were notably slower compared to other clusters, impacting the performance of the US-ORD-1 Object Storage cluster and affecting multiple customers. Our investigation identified a configuration issue as the root of the problem, where a machine with an incorrect configuration was inadvertently left in rotation, leading to degraded performance across the cluster. To address the issue, we promptly removed the misconfigured machine from the production environment, and the cluster’s performance returned to normal, with pre-incident levels restored at approximately 02:40 UTC on January 13, 2025.
We are conducting a comprehensive root cause analysis to identify preventive measures and ensure such incidents do not recur, with enhancements to our monitoring and configuration validation processes already underway. We sincerely apologize for the inconvenience this incident caused and appreciate your patience and support.
At Akamai, we are dedicated to improving the reliability and performance of our systems and services.
This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: At this time we have been able to correct the issues affecting the Object Storage 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.

Investigating: We are continuing to investigate the issue. Subsequent updates will be posted as progress is made.

Investigating: Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.

Resolved: We haven’t observed any additional issues with the Object Storage service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.

Monitoring: Our team has identified an issue which introduced latency to the Object Storage service between 14:18 UTC and 16:29 UTC on January 15, 2025. At this time we have been able to correct the issues affecting the Object Storage 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.