Issues with preempted Managed Kubernetes nodes in all regions
minor- Started
- Oct 2, 11:31 AM EDT
- Resolved
- Oct 5, 11:54 AM EDT
- Duration
- 72h 23m
Nebius's updates (3)
- investigating · Oct 2, 11:31 AM EDT
We are investigating an issue affecting Managed Kubernetes node groups in all regions. Preemptible nodes that were in a preempted (stopped) state on October 1 or earlier do not auto-start when capacity becomes available. Manually stopping or starting a node group node does not take effect. Running workloads are not affected. A fix is being rolled out.
- identified · Oct 2, 11:50 AM EDT
The issue has been identified and a fix has been prepared. The issue has limited impact and does not affect running workloads. To avoid possible disruption of customer production workloads over the weekend, deployment is scheduled for early next week. If you are experiencing any issues, please reach out to our support team, and we will be glad to assist you.
- resolved · Oct 5, 11:54 AM EDT
This incident has been resolved.
What our checks recorded
We checked Nebius 576 times from Nebius's start time to its resolution, once every five minutes. Every one of them reached Nebius's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 169 ms, against 147 ms over the 24 hours before. Nebius posted the incident at Oct 2, 11:31 AM EDT.
Updates are Nebius's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗