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 months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
Jul 03, 2026 - 13:55 UTC
Update - We are currently deploying a fix for this issue in phases, which will take several months to complete. We will continue to share updates on our progress as the mitigation efforts move forward.
May 26, 2026 - 21:17 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.
May 13, 2026 - 20:59 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 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
Cloud 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
FR-PAR-2 (Paris 2) Operational
US-IAD-2 (Washington 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
Observability Operational
Akamai Cloud Pulse (ACLP) - Alerts Operational
Akamai Cloud Pulse (ACLP) - Logs Operational
Akamai Cloud Pulse (ACLP) - Metrics Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Scheduled Maintenance for Linode Cloud Manager, API, CLI Aug 19, 2026 04:00-05:30 UTC

The Linode Cloud Manager, API, and CLI will be offline for scheduled maintenance between 04:00 UTC and 05:30 UTC on August 19, 2026. 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.
Posted on Jul 09, 2026 - 14:53 UTC
Jul 11, 2026

No incidents reported today.

Jul 10, 2026

No incidents reported.

Jul 9, 2026
Emerging Service Issue - Cloud Manager
Postmortem - Read details
Jul 10, 12:31 UTC
Resolved - We haven't observed any additional issues with the Cloud Manager logins 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.
Jul 9, 18:21 UTC
Monitoring - 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 open a Support ticket, please call us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com.
Jul 9, 17:49 UTC
Update - We are continuing to investigate this issue. We will provide an update within the next 30 minutes.
Jul 9, 17:24 UTC
Investigating - Our team is investigating an emerging service issue affecting Cloud Manager logins. We will share additional updates as we have more information.
Jul 9, 16:57 UTC
Jul 8, 2026
Service Issue - ACLP Metrics
Resolved - We haven’t observed any additional issues with the Cloud Pulse Metrics (ACLP Metrics) service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jul 8, 12:26 UTC
Update - We are continuing to monitor for any further issues.
Jun 30, 00:02 UTC
Monitoring - 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 open a Support ticket for assistance.
Jun 26, 21:13 UTC
Update - We are continuing to investigate this issue.
Jun 26, 20:04 UTC
Update - We are continuing to investigate this issue. We will provide further updates as we have more information.
Jun 26, 19:08 UTC
Update - We are continuing to investigate this issue. We will share additional updates as we have more information.
Jun 26, 18:19 UTC
Investigating - 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.
Jun 26, 17:35 UTC
Jul 7, 2026
Emerging Service Issue - Managed Databases - All Regions
Resolved - This incident has been resolved.
Jul 7, 15:31 UTC
Investigating - 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.
Jul 6, 18:04 UTC
Jul 6, 2026
[Fragnesia] Linux Privilege Escalation Vulnerability
Resolved - We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected systems. Customers can find more information and step-by-step instructions here:

https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
https://www.linode.com/docs/guides/dirty-frag-mitigation/

We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please contact us at 855-454-6633 (+1-609-380-7100 Intl.) or email support@linode.com for assistance.
Jul 6, 14:42 UTC
Update - We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.

We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.

[1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
[2] https://www.linode.com/docs/guides/dirty-frag-mitigation/
Jun 5, 20:24 UTC
Update - We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.

We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.

[1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
[2] https://www.linode.com/docs/guides/dirty-frag-mitigation/
May 15, 17:30 UTC
Investigating - 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 vulnerability across our product portfolio and internal systems.

As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.

As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.

[1] https://github.com/v12-security/pocs/tree/main/fragnesia
[2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md
[3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
May 13, 21:02 UTC
[DirtyFrag] Linux Privilege Escalation Vulnerability
Resolved - We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected systems. Customers can find more information and step-by-step instructions here:

https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
https://www.linode.com/docs/guides/dirty-frag-mitigation/

We encourage all customers to review the article and apply the appropriate mitigations to their environments. If you have questions or need assistance, please contact us at 855-454-6633 (+1-609-380-7100 Intl.) or email support@linode.com for assistance.
Jul 6, 14:41 UTC
Update - We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.

We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.

[1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
[2] https://www.linode.com/docs/guides/dirty-frag-mitigation/
Jun 5, 20:23 UTC
Update - We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions.

We will provide another update when more OS images have been updated and/or additional attack vectors are discovered.

[1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
[2] https://www.linode.com/docs/guides/dirty-frag-mitigation/
May 15, 17:28 UTC
Update - We have updated our latest Linode kernel to version 7.0.5, which contains the upstream fix from kernel.org for the DirtyFrag vulnerabilities as well as the previous fixes for the recent CopyFail vulnerability. This kernel is available in Cloud Manager and we recommend customers using the Linode-compiled kernel update their configurations to this kernel. We are in parallel tracking the upstream Linux distributions and will provide another update when fixed versions have been released.
May 9, 14:40 UTC
Investigating - 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 across our product portfolio and internal systems.

As with “CopyFail”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers.

As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected.

[1] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md
[2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/
May 8, 13:40 UTC
Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026

Unresolved incident: Service Issue - GPU and VPU Booting issues.

Jul 2, 2026

No incidents reported.

Jul 1, 2026
Service Issue - Linode Automated Networking
Resolved - We haven’t observed any additional issues with the Linode Automated Networking service, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jul 1, 18:28 UTC
Monitoring - 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.
Jul 1, 18:09 UTC
Identified - 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 still manually configure networking via the LISH console to mitigate this issue. Please see our guide on manual network configuration on a Compute Instance.

We will share additional updates as we have more information.
Jul 1, 17:21 UTC
Jun 30, 2026
Service Issue - Block Storage - Singapore Expansion, SP (sg-sin-2)
Postmortem - Read details
Jul 2, 16:29 UTC
Resolved - We haven’t observed any additional issues with the Block Storage service in Singapore Expansion, SP (sg-sin-2), and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Jun 30, 23:22 UTC
Monitoring - 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 open a Support ticket for assistance.
Jun 30, 22:10 UTC
Update - We are continuing to work on a fix for this issue.
Jun 30, 21:36 UTC
Identified - Our team has identified the issue affecting the Block Storage service in our Singapore Expansion, SP (sg-sin-2) data center. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Jun 30, 20:36 UTC
Update - We are continuing to investigate this issue.
Jun 30, 19:55 UTC
Investigating - 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.
Jun 30, 18:54 UTC
Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage