Linode experienced a notice incident on May 19, 2026, lasting 4h 38m. The incident has been resolved; the full update timeline is below.
Update timeline
- identified May 19, 2026, 07:48 PM UTC
Our team is investigating an emerging service issue affecting GPU provisioning in all regions. At this time deployment of RTX PRO 6000 Blackwell plans in unavailable. We will share additional updates as we have more information.
- identified May 19, 2026, 09:06 PM UTC
The issue with deployment of RTX PRO 6000 Blackwell plans appears to have started around 15:00 UTC on May 19, 2026. We are actively working to deploy an API hotfix that is expected to be rolled out within 1 hour. We apologize for the impact.
- monitoring May 19, 2026, 09:58 PM UTC
At this time we have been able to correct the issues affecting GPU provisioning in all regions as of 21:27 UTC. on May 19th. We will be monitoring this to ensure that it remains stable. If you continue to experience problems, please open a Support ticket for assistance.
- resolved May 20, 2026, 12:27 AM UTC
We haven’t observed any additional issues with the GPU provisioning in all regions, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
- postmortem May 25, 2026, 05:35 PM UTC
On May 19, 2026, at 18:26 UTC, we identified an issue impacting the creation and re-provisioning of Linode instances using any of the four RTX PRO 6000 Blackwell \(g3-gpu-rtxpro6000-blackwell\) plans, resulting in API errors. These failures caused a denial of service for customers attempting to deploy g3-gpu-rtxpro6000-blackwell instances via the Cloud Manager or API. After the initial investigation SMEs determined that the cause of the issue was a logic error within a recent APIv4 update. Specifically, a validation check intended only for RDMA-enabled networking was incorrectly applied to standard Blackwell GPU plans. This caused the API to reject creation requests that did not meet specific RDMA configurations, even when those configurations were not required for the selected plan. With the issue identified, our engineering team developed and tested a hotfix to correct the plan-validation logic. Deployment of the fix began shortly after, and broader customer impact was mitigated as of 21:36 UTC on May 19, 2026, following successful verification in all regions. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and we are currently reviewing our automated testing to prevent similar recurrences.