Skip to main content
Akamai Cloud (Linode)

Service Issue - GPU and VPU Booting issues

Degraded Lasted 309d 6h · started · Akamai Cloud (Linode)'s page

Level
confirmed
Worst impact
Degraded
Down Index
32of 100

What to do

  • Check whether your product depends on Akamai Cloud (Linode). 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 309d 6h it lasted.

    Anything that failed between 2025-12-03 15:15 UTC and 2026-10-08 21:26 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) 16

  1. investigating

    Our team is investigating an emerging service issue affecting booting up GPU plans. We will share additional updates as we have more information.

    provider

  2. 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.

    provider

  3. identified

    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.

    provider

  4. identified

    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.

    provider

  5. identified

    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.

    provider

  6. identified

    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.

    provider

  7. identified

    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.

    provider

  8. identified

    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.

    provider

  9. identified

    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.

    provider

  10. identified

    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.

    provider

  11. identified

    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.

    provider

  12. identified

    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.

    provider

  13. identified

    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.

    provider

  14. identified

    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.

    provider

  15. identified

    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.

    provider

  16. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-411a17570a

Is Akamai Cloud (Linode) still down?

No, this incident was resolved 2026-10-08 21:26 UTC. For Akamai Cloud (Linode)'s live state, see https://down.guide/linode.

How long did it last?

309d 6h, from 2025-12-03 15:15 UTC to 2026-10-08 21:26 UTC, by the times Akamai Cloud (Linode) posted.

What caused it?

Akamai Cloud (Linode) hasn't published a root cause. If it does, it shows here.

Where does this come from?

Akamai Cloud (Linode)'s official status page, https://status.linode.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.