Linode incident

Service Issue - GPU and VPU Booting issues

Linode is currently experiencing a minor incident, which began 165d ago. The vendor's full update timeline is below.

Started
Dec 03, 2025, 03:15 PM UTC
Resolved
Ongoing
Duration
● 164d 13h
Detected by Pingoru
Dec 03, 2025, 03:15 PM UTC

Update timeline

  1. investigating Dec 03, 2025, 03:15 PM UTC

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

  2. identified Dec 03, 2025, 04:48 PM 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.

  3. identified Dec 04, 2025, 08:51 PM 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.

  4. identified Dec 17, 2025, 01:40 PM 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.

  5. identified Jan 05, 2026, 05:16 PM 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.

  6. identified Jan 05, 2026, 07:30 PM 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.

  7. identified Feb 03, 2026, 03:34 PM 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.

  8. identified Feb 19, 2026, 04:41 PM 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.

  9. identified Feb 26, 2026, 03:42 PM 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.

  10. identified Mar 19, 2026, 08:13 PM 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.

  11. identified Apr 06, 2026, 01:39 PM 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.

  12. identified Apr 15, 2026, 03:12 PM 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.

  13. identified May 13, 2026, 08:59 PM 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.