Linode (Akamai Cloud)
Our team is investigating packet loss on some paths from the in-maa & in-bom-2 data centers into the US region. During this time, users may experience connection timeouts and errors with services traversing between India and United States regions. We will share additional updates as we have more information.
Our team is investigating an issue affecting the Block Storage service in several data center regions. This issue largely impacts attaching and detaching Block Storage volumes. During this time, users may experience volume attach/detach hangs, timeouts and errors with this service. We will share additional updates as we have more information.
Cause: On 27 July 2026 at 3:30 UTC, Akamai observed an increase in errors when connecting to the Linode hosting database, primarily affecting Block Storage volume attachments. This resulted in host job failures and limited customer impact, with some users experiencing error messages and interrupted workflows. Elevated timeout…
Remediation: A fix has been implemented and we are monitoring the results.
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.
Cause: 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 unex…
Remediation: 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Our team is investigating an issue affecting the Object Storage service. During this time, users may experience connection timeouts and errors with this service.
Cause: 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.…
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 con…
Our team is investigating an emerging service issue affecting the API and CLI. We will share additional updates as we have more information.
Cause: 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 ser…
Remediation: 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (…
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.
Our team is investigating an emerging service issue affecting Cloud Manager logins. We will share additional updates as we have more information.
Cause: On July 9, 2026, at 15:43 UTC, customers were unable to login to [cloud.linode.com](http://cloud.linode.com) using username and password. Customers were getting "wrong password" error message. Investigation revealed that the issue was due to an internal certificate issue. To mitigate the impact, we fixed the certifi…
Remediation: At this time we have been able to correct the issue affecting the Cloud Manager logins. We will be monitoring this to ensure that the service remains stable. If you are still experiencing issues and unable to <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (…
Our team is investigating an emerging service issue affecting Managed Databases across all regions. Customers may experience latency when provisioning new databases or deleting existing ones. There is no observed impact to the performance or availability of active, running databases at this time. We will provide updates as more information becomes available.
Our team is investigating a service issue that affects the auto configuration of networking on Linodes by Network Helper to fail. During that time, some users may have Linodes provision but appear to have no connectivity. This also can impact Linodes created by the Linode Kubernetes Engine and impact autoscaling or provisioning of clusters. Customers can sti…
Remediation: A fix has been implemented to resolve the automated network configuration issue on Linodes using Network Helper. We recommend rebooting your Linode to restore full network functionality. We are actively monitoring the results to ensure continued stability.
Our team is investigating an emerging issue affecting the Block Storage service in our Singapore Expansion, SP (sg-sin-2) data center. During this time, users may experience connection timeouts and errors with this service. We will share additional updates as we have more information.
Cause: On June 30, 2026, between approximately 17:30 UTC and 21:45 UTC, users may have experienced connection timeouts and errors related to the Block Storage service in Singapore Expansion, SP \(sg-sin-2\). The issue began when one host in the cluster was taken down for maintenance while another host unexpectedly encountere…
Remediation: At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Our team is investigating an issue affecting the Cloud Pulse Metrics (ACLP Metrics), specifically impacting Managed Database Metrics reporting. The issue appears to be intermittent. We will share additional updates as we have more information.
Remediation: We have not observed a recurrence of the issue affecting the Cloud Pulse Metrics (ACLP Metrics) for several hours. Our team will continue to monitor the service closely while we investigate the underlying cause. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Sup…
Our team is investigating an issue affecting connectivity in our US-IAD data center. During this time, users may experience intermittent connection timeouts and errors for services deployed in this data center. We will share additional updates as we have more information.
Our team is investigating an emerging service issue affecting migrations and resizes in all regions. At this time, Linode migrations and plan resizes may be delayed. We will share additional updates as we have more information.
Remediation: A fix has been implemented and we are monitoring the results.
Our team is investigating an emerging service issue that is causing intermittent boot failures on GPU Instances in all Regions. We will share additional updates as we have more information.
Cause: On June 23, 2026, following a global software deployment, we identified an issue causing intermittent boot failures specifically for GPU Linodes. The impact was limited to instances where multiple GPU Linodes attempted to boot simultaneously. During the impact window customers could have experienced localized disruptio…
Remediation: At 20:32 UTC on June 24th, 2026 we have been able to correct the issue that is causing intermittent boot failures on GPU Instances in all Regions. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support…
Between approximately 08:12 UTC and 12:35 UTC on June 24, 2026, attempting to create/autoscale Linodes using a Debian distribution may have failed due to a stale InRelease file in an upstream repository. We have mitigated the issue by updating our mirror endpoint to a healthy repository. If you continue to experience problems, please <a href="https://cloud.l…
Cause: Our upstream third-party Debian repo failed to sync with their own upstream repo chain for an unknown reason. The InRelease files for Debian packages were left to expire starting at approximately 08:12 UTC on June 24, 2026, preventing any Debian packages from getting installed. We didn't have programmatic visibility at…
Our team is investigating an emerging service issue affecting networking in US-MIA (Miami). We will share additional updates as we have more information.
Cause: On June 16, 2026 Akamai investigated an instance of performance degradation and connectivity slowness observed affecting applications within the Miami compute environment. This event occurred between around 13:37 UTC and 14:20 UTC on June 16, 2026. The Investigation revealed a configuration change on an Akamai device…
Our team is investigating an issue affecting the Longview service. During this time, users may experience "waiting for data" in cloud manager and might not see the expected metrics. We will share additional updates as we have more information.
Cause: Starting around 23:15 UTC on June 15, 2026, some customers were unable to access the Longview graph dashboard. The investigation revealed that Linodes were unable to reach the Longview endpoint and were failing to report data. The impact was limited to reading the existing reporting data only and there was no permanent…
Remediation: A fix has been implemented and we are monitoring the results.
Our team is investigating an emerging service issue affecting Linode Migrations in all regions. Migrations might be slow or pending for long time. We will share additional updates as we have more information.
Remediation: A fix has been implemented and we are monitoring the results.
We are currently investigating an emerging service issue affecting LKE Enterprise clusters across all regions. During this time, users may experience failures when deploying new clusters or upgrading existing ones. Our team is working to resolve this, and we will provide updates here as they become available.
Our team is investigating an upstream emerging service issue affecting our Support phone line due to problems with an upstream provider. We will share additional updates as we have more information. If you are having difficulty reaching us over the phone during this time, please reach us through a ticket.
Our team is investigating an issue affecting the Block Storage service in our Newark, US data center. During this time, users may experience connection timeouts, latency and errors with this service. We will share additional updates as we have more information.
Cause: Between 22:50 UTC on June 2, 2026 and 19:00 UTC on June 3, 2026, some customers experienced intermittent performance degradation and long access times when interacting with the Compute Block Storage cluster in Newark, US. During this period, intermittent component instability triggered intensive background recovery ope…
Remediation: At this time we have been able to correct the issues affecting the Block Storage service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Our team has identified issues with the Community Site (https://www.linode.com/community/questions/). During this time, the page has been moved under maintenance mode. We will share additional updates as we have more information.
Remediation: At this time we have been able to correct the issue affecting connectivity to the Community Site. We will be monitoring this to ensure that connectivity remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Starting at around 10:07 UTC on May 29, 2026, Object Storage in London became unavailable. Affected customers were unable to access Object Storage during this time, and may have seen 500 or similar errors. This occurred as the result of an issue with a planned router upgrade. The router has since been brought back online, and we can confirm that the issue w…
Cause: Between 10:13 UTC and 10:22 UTC on May 29, 2026, customers using Object Storage \(OBJ\) in London experienced 5xx errors when trying to access content stored in that location. While attempting to isolate a separate packet loss issue, Akamai sequentially upgraded 2 pairs of routers. The first pair of routers was upgrade…
We are investigating a service issue affecting traffic in our Paris data center. We will share additional updates as we have more information.
Cause: On May 22, 2026 between approximately 09:10 and 11:30 UTC, connectivity issues were experienced in Paris \(FR-PAR3\) datacenter. During the impact window, customers may have experienced intermittent connection timeouts and errors for services deployed in the Paris datacenter. Our investigation established that connect…
Remediation: The issue subsided by 11:30 UTC on May 22, 2026, the impact was observed between 09:10 UTC to 11:30 UTC on May 22, 2026. We are actively monitoring to ensure that the service remains stable . If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for…
Our team is investigating an emerging service issue affecting GPU provisioning in all regions. At this time deployment of RTX PRO 6000 Blackwell plans in unavailable. We will share additional updates as we have more information.
Cause: On May 19, 2026, at 18:26 UTC, we identified an issue impacting the creation and re-provisioning of Linode instances using any of the four RTX PRO 6000 Blackwell \(g3-gpu-rtxpro6000-blackwell\) plans, resulting in API errors. These failures caused a denial of service for customers attempting to deploy g3-gpu-rtxpro6000…
Remediation: At this time we have been able to correct the issues affecting GPU provisioning in all regions as of 21:27 UTC. on May 19th, 2026. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for…
Our team is investigating an emerging service issue affecting Linodes booting across all regions. We will share additional updates as we have more information.
Cause: On May 15, 2026, at 18:18 UTC, we identified an issue impacting the deployment of Linodes that relied on StackScripts \(including all newly created Linode Kubernetes Engine \(LKE\) and \(LKE-E\) nodes\), resulting in deployment failures. These deployment failures resulted in Linodes created with StackScripts to be unbo…
We are currently investigating an issue causing delays to both cold and live migrations globally. A number of migrations are stuck, and additional migrations are queued and pending across all regions. Customer Impact: Cold and live migrations along with linode resize may be delayed or unresponsive. We recommend avoiding initiating new migrations and resizes…
Cause: Starting around 04:00 UTC on May 14, 2026, Akamai identified an issue affecting Linode migration operations, including live, cold, and scheduled migrations. As a result, some customers experienced delays in migration processing, and customers undergoing certain migrations were temporarily unable to access their instanc…
Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the v…
Our team is investigating an issue affecting connectivity in our NL-AMS 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.
Remediation: At this time we have been able to confirm that no customers should be impacted by the issues affecting connectivity in our NL-AMS data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please <a href="https://cloud.linode.com/support/tickets">open a Support ticke…
Our team became aware of an issue affecting the Cloud Pulse Metrics for Managed Databases (ACLP Metrics) for two short periods on May 12 and May 14, 2026, and a fix has been applied. We haven’t observed any additional issues with the ACLP Metrics service, and will now consider this incident resolved. If you continue to experience problems, please <a href="ht…
Cause: Between May 12 and May 14, 2026, Akamai Cloud Pulse \(ACLP\) experienced two related service interruptions that temporarily disrupted the ingestion and display of telemetry metrics specifically for Managed Databases. * Window 1: May 12, 23:15 UTC – May 13, 00:11 UTC * Window 2: May 14, 06:47 UTC – 07:33 UTC During th…
Our team is investigating an issue affecting connectivity in our AP-West (Mumbai) and IN-MAA (Chennai) data centers. During this time, users may experience intermittent connection timeouts and errors for all services deployed in these data centers. We will share additional updates as we have more information.
Cause: On May 12, 2026, at approximately 14:50 UTC, Akamai began experiencing congestion and packet loss affecting traffic between India and Europe over Internet Service Provider network paths servicing our Mumbai and Chennai data centers. Customers may have seen intermittent connection timeouts and errors in the affected reg…
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability acro…
Akamai is aware of the recently disclosed “Copy Fail” vulnerability (CVE-2026-31431). We are assessing the issue and are working to address it across our product portfolio and internal systems. While we have not observed any related malicious exploits targeting our infrastructure, Akamai continuously works to reduce risks and enhance our security posture. We…
We are aware that some customers have been experiencing 403 (InvalidAccessKeyId) errors when attempting to access object storage, beginning yesterday evening. We will share additional updates as we have more information.
Cause: Between approximately 09:15 UTC on April 28, 2026 and 16:54 UTC on April 29, 2026 customers could have experienced issues with their Object Storage key pairs, including: key creation and validation, Object Storage access with their keys. The impact was seen throughout multiple data centers. Our investigation establish…
Our team is investigating an emerging service issue affecting the network and connectivity in our Chennai (IN-MAA) data center. Customers may see intermittent delays and timeouts during peak traffic hours in the region. If you are seeing impact that may be related, please <a href="https://cloud.linode.com/support/tickets?dialogOpen=true">open a Support Tick…
Cause: At approximately 3:30 UTC on April 28, 2026, we experienced a router failure in our Chennai data center, which, when paired with a separate network hardware component temporarily operating at a reduced capacity, resulted in intermittent delays or timeouts for Compute customers accessing Linodes and other resources in t…
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine (LKE) service across multiple regions. We will share additional updates as we have more information.
Cause: On April 24, 2026, between 17:57 UTC and 23:36 UTC, NodeBalancer infrastructure experienced a service degradation caused by NodeBalancer configuration identifiers exceeding a programmed limit. This issue degraded functionality for newly created and updated NodeBalancers and rendered Linode Kubernetes Engine \(LKE\) clu…
Remediation: At this time we have been able to correct the issues affecting the NodeBalancer service at 23:36 UTC on April 24, 2026. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a ticket</a> with our Support Team.
Our team is investigating an emerging service issue impacting connectivity in Frankfurt (DE-FRA-2). We will share additional updates as we have more information.
Cause: On April 20, 2026, approximately between 11:05 UTC and 13:10 UTC, Frankfurt \(DE-FRA-2\) data center experienced degraded connectivity and performance issues for Compute services, including Linode and Object Storage. During this time, customers in the Frankfurt region may have experienced packet loss or connectivity is…
Remediation: A fix has been implemented and we are monitoring the results.
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.
Cause: Starting at 11:45 UTC on April 16, 2026, customers using Linode Kubernetes Engine \(LKE\) and Linode Kubernetes Engine Enterprise \(LKE-E\) began to experience issues deploying LKE and LKE-E clusters and nodes. The affected customers were unable to deploy new nodes, which also prevented them from recycling nodes and au…
Remediation: 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 <a href="https://cloud.linode.com/support/ticket…
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 dur…
Cause: On April 15, 2026, at 16:07 UTC, we identified an issue affecting the Linode platform, where multiple hosts began experiencing Linode VM guest orchestrator service failures. This issue disrupted new Linode jobs, Linode Kubernetes Engine \(LKE\) scaling, and related operations. Customers may have noticed slow or incompl…
Remediation: 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 <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a>, please call us at 855-454-6633 (…
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 addit…
Cause: On March 9, 2026, at 20:02 UTC, we identified an issue impacting Dedicated CPU plan Linodes, resulting in boot failures and resource allocation errors across multiple data centers. The problem was first reported by a customer who was unable to boot a newly provisioned Dedicated CPU Linode. We began investigating the is…
Our team is investigating an emerging service issue affecting networking in US-IAD (Washington). We will share additional updates as we have more information.
Cause: Starting around 22:55 UTC on April 9, 2026, customers were unable to access services hosted in the US-IAD \(Washington\) data center \(DC\). The investigation revealed that the issue was caused by network connectivity issues, which would have resulted in connection timeouts and/or errors for services deployed in this d…
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.
Remediation: 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.
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.
Our team is investigating an emerging service issue affecting the deployment of new compute instances where the swap disk size is set to 0. This is also impacting our Managed Databases service. We will share additional updates as we have more information.
Our team has identified the issue affecting connectivity in our Jakarta data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Cause: On March 20, 2026, at approximately 10:40 UTC, the Jakarta, ID \(id-cgk\) data center experienced power fluctuations that caused outages across all services in Jakarta, with downstream impacts to services in the Singapore Expansion, SP \(sg-sin-2\), and Melbourne, AU \(au-mel\) regions. The facility switched to backup…
Remediation: At this time we have been able to correct the issues affecting connectivity in our Jakarta, ID data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Our team is investigating an issue affecting the Linode Kubernetes Engine Enterprise (LKE-E) service. We will share additional updates as we have more information.
Cause: Between approximately 01:00 and 14:12 UTC on March 17, 2026, customers were unable to deploy new Linode Kubernetes Engine Enterprise \(LKE-E\) clusters in the Chicago \(us-ord\) region. This was caused by exceeding the allowable number of DNS records in the DNS zone used for provisioning, which prevented the creation o…
Remediation: At this time we have been able to correct the issues affecting the LKE-E service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Our team is investigating an emerging service issue affecting networking in our Washington, DC location (US-IAD). We will share additional updates as we have more information.
Cause: _On March 13, 2026, between approximately 17:35 UTC and 18:54 UTC, our Washington \(US-IAD\) data center experienced connectivity issues. During this time, customers may have noticed disruptions across all services hosted in this data center._ _Our investigation revealed that three servers previously used for test…
Our team is investigating an emerging service issue affecting the deployment of new LKE Enterprise Clusters in JP, OSA (Osaka). We will share additional updates as we have more information.
Cause: Starting around 19:15 UTC on March 12, 2026, customers were unable to create Linode Kubernetes Engine for Enterprise \(LKE-E\) clusters and unable to perform administrative tasks such as LKE-E version upgrades, Control Plane ACL changes, etc., in the Osaka data center \(JP-OSA\). The creation process was stalled indefi…
Remediation: At this time we have been able to correct the issues affecting the LKE service. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.
Our team is investigating an emerging service issue affecting compute hosts in IAD (Washington, DC). We will share additional updates as we have more information.
Cause: Beginning at 18:09 UTC on March 9, 2026, approximately 25% of Compute hosts in our IAD3 \(Washington DC\) data center experienced degraded network connectivity due to the application of an updated routing configuration intended to improve network performance. This updated router configuration was extensively tested and…
Remediation: At this time we have been able to correct the issues affecting connectivity in our IAD (Washington, DC) data center. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.