Is Linode down?

Our team is currently investigating a connectivity issue affecting Linodes in the Italy (Milan) region. During this time, existing Linodes in this location may be unreachable. Please note that creating new Linodes is functioning normally and remains unaffected.

We are continuing to investigate this issue. We will provide the next update as we make progress.

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

At this time, we have been able to correct the issues affecting connectivity in our Milan (Italy) 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.

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

Starting around 00:33 UTC on July 20, 2026, some hosts in the Milan, Italy data center became unavailable, impacting customer access to Linodes. The investigation identified that this issue occurred during scheduled router firmware updates. While we follow a phased upgrade process to prevent service disruption, an unexpected intersection of concurrent maintenance activities led to a temporary loss of network connectivity for the affected hosts. Service was fully restored by 02:16 UTC on July 20, 2026, and all systems are now operating as expected. Internally, we are reviewing our change management and maintenance scheduling procedures to ensure better coordination and prevent similar impacts in the future. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence. 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.

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

Our team has identified the issue affecting the Object Storage service. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.

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.

On July 18, 2026, between approximately 00:30 UTC and 04:00 UTC, users might have experienced 5xx errors while trying to create a new bucket in the Object Storage for the following endpoints. * [us-ord-1.linodeobjects.com](http://us-ord-1.linodeobjects.com) * [us-lax-1.linodeobjects.com](http://us-lax-1.linodeobjects.com) * [us-iad-1.linodeobjects.com](http://us-iad-1.linodeobjects.com) * [us-sea-1.linodeobjects.com](http://us-sea-1.linodeobjects.com) * [fr-par-1.linodeobjects.com](http://fr-par-1.linodeobjects.com) ‌The issue began when the infrastructure supporting Object Storage entered a degraded state across all nodes. This prevented the service from processing requests, resulting in failures during bucket creation operations. ‌To mitigate the impact, we have applied a fix at the backend system responsible for bucket creation. The impact was mitigated following this action. ‌Our subject matter experts are investigating the root cause and will take appropriate preventive actions. ‌We apologize for the impact and appreciate your patience and ongoing support. We are making configuration and operational changes to our systems to help prevent this from happening again, and remain committed to continuous improvement. ‌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.

Our team investigated an issue that affected connectivity in our US-MIA (Miami) data center between 21:20 UTC and approximately 23:28 UTC on July 15, 2026. During this window, users may have experienced degraded networking performance and packet loss for Compute services deployed in this region. The issue was resolved after we implemented a fix. We are continuing to work with our third-party service provider to confirm the root cause, as initial evidence points to a campus cross-connect (dark fiber) outage on their infrastructure.

Our team is investigating an emerging service issue affecting the API and CLI. We will share additional updates as we have more information.

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.

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 [email protected].

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

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 [email protected] for assistance.

On July 14, 2026, at 10:57 UTC, Akamai identified an increase in 502 errors and latency affecting customers using the Linode API, CLI, and Cloud Manager. This disruption resulted in moderate service impact, with customers reporting elevated error rates. Our initial investigation traced the issue to latency with IAM services, which was resolved, but elevated errors persisted.  Further analysis by relevant subject matter experts determined that the incident was triggered by a manual failback to the Cloud IAM primary load balancer from the secondary load balancer. This action was prompted by a warning alert indicating that the secondary load balancer was acting as the keepalived master. The manual process of starting and stopping services to initiate the failback differed from the automated process and led to a cascade of stale GRPC connections, causing increased latency and API errors. Restarting the API servers cleared the stale connections and restored normal operations. Customer impact was mitigated by approximately 13:10 UTC on July 14, 2026. To prevent recurrence, Akamai is investigating why the manual failback caused this behavior. The team is considering implementing a drain command to clear GRPC connections during failover and setting up alerts to detect stale connections for proactive intervention. However, the immediate focus remains on understanding the root cause, with alerting and automation planned for later phases. Several customers have confirmed resolution across their deployments. Akamai will continue to monitor system health and await additional customer feedback before declaring full recovery.  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.

Our team has identified an emerging service issue affecting host jobs for some hosts across all regions. Linode connectivity is *not impacted*, but some host-level jobs, such as backups or attempts to power on or off your services may be delayed. We will share additional updates as we have more information.

This incident has been resolved.