Service Issue: RTX 4000 Ada GPU Errors Across Multiple Regions

What to do

• Check whether you use Akamai Cloud (Linode) US-ORD (Chicago) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, SG-SIN-2 (Singapore 2) Linode Kubernetes Engine in apac, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 16h 4m it lasted.

  Anything that failed between 2026-03-05 02:07 UTC and 2026-03-05 18:11 UTC may need a replay.

• Subscribe to Akamai Cloud (Linode)'s feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=linode works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai Cloud (Linode) 9

1. investigatingMar 5, 2026, 2:07 AM UTC

   We are investigating a critical service issue affecting NVIDIA RTX 4000 Ada GPU nodes across multiple regions, including Osaka (osa1), Seattle (sea1), and Chicago (ord1). Affected GPU nodes may report an unrecoverable error state leading to failures in Vulkan initialization and GPU-accelerated workloads. Additionally, some LKE clusters in the Osaka region are currently experiencing Control Plane connectivity issues, resulting in timed-out API requests and errors. Our engineering teams are currently investigating the root cause, focusing on a potential regression in the underlying host hypervisor or GPU firmware. We will provide more information as it becomes available

   provider

2. investigatingMar 5, 2026, 5:48 AM UTC

   Our subject matter experts are actively investigating the issue. We will provide the next update as progress is made.

   provider

3. investigatingMar 5, 2026, 6:55 AM UTC

   We are continuing to investigate the issue. We will provide the next update as progress is made.

   provider

4. monitoringMar 5, 2026, 7:34 AM UTC

   Our team has identified the issue affecting the service and implemented a fix. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.

   provider

5. investigatingMar 5, 2026, 10:50 AM UTC

   We are aware of a recurrence of this issue across multiple regions. We are continuing to investigate and will provide the next update as progress is made.

   provider

6. investigatingMar 5, 2026, 2:48 PM UTC

   We are continuing to investigate and will provide the next update as progress is made.

   provider

7. identifiedMar 5, 2026, 4:23 PM UTC

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

   provider

8. monitoringMar 5, 2026, 5:01 PM UTC

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

   provider

9. resolvedMar 5, 2026, 6:11 PM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.