Minor impactResolvedCloud

Linode incident: Service Issue - GPU and VPU Booting issues

Linode reported this minor-impact incident on its official status page on Dec 3, 2025, 15:15 UTC. It was resolved after 309d 6h.

Right now Linode is operational. Live Linode status →

🔔 Get alerted when Linode has issuesFree · email alerts · no credit card
Dec 3, 2025, 15:15 UTC
started
Oct 8, 2026, 21:26 UTC
resolved
309d 6h
duration
Minor
impact
  1. resolvedOct 8, 2026, 21:26 UTC

    We haven’t observed any additional issues with GPU plans, and will now consider this incident resolved. If you continue to experience problems, please <a href="https://cloud.linode.com/support/tickets">open a Support ticket</a> for assistance.

  2. identifiedJul 3, 2026, 13:55 UTC

    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.

  3. identifiedMay 26, 2026, 21:17 UTC

    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.

  4. identifiedMay 13, 2026, 20:59 UTC

    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.

  5. identifiedApr 15, 2026, 15:12 UTC

    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.

  6. identifiedApr 6, 2026, 13:39 UTC

    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.

  7. identifiedMar 19, 2026, 20:13 UTC

    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.

  8. identifiedFeb 26, 2026, 15:42 UTC

    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.

  9. identifiedFeb 19, 2026, 16:41 UTC

    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.

  10. identifiedFeb 3, 2026, 15:34 UTC

    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.

  11. identifiedJan 5, 2026, 19:30 UTC

    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.

  12. identifiedJan 5, 2026, 17:16 UTC

    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.

  13. identifiedDec 17, 2025, 13:40 UTC

    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.

  14. identifiedDec 4, 2025, 20:51 UTC

    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.

  15. identifiedDec 3, 2025, 16:48 UTC

    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.

  16. investigatingDec 3, 2025, 15:15 UTC

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

What APIStatus.watch saw

  • Oct 7, 2026, 09:03 UTCoperational → degraded
  • Oct 7, 2026, 14:04 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Linode have incidents?

Linode reported 13 incidents in the last 90 days. A typical incident lasted 2h 53m. See Linode's uptime and incident history