Nebius incident

Issues with preempted Managed Kubernetes nodes in all regions

Minor Resolved View vendor source →

Nebius experienced a minor incident on October 2, 2026 affecting Managed Service for Kubernetes® and Managed Service for Kubernetes® and 1 more component, lasting 3d. The incident has been resolved; the full update timeline is below.

Started
Oct 02, 2026, 03:31 PM UTC
Resolved
Oct 05, 2026, 03:54 PM UTC
Duration
3d
Detected by Pingoru
Oct 02, 2026, 03:31 PM UTC

Affected components

Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®Managed Service for Kubernetes®

Update timeline

  1. investigating Oct 02, 2026, 03:31 PM UTC

    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.

  2. identified Oct 02, 2026, 03:50 PM UTC

    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.

  3. resolved Oct 07, 2026, 02:02 PM UTC

    This incident has been resolved.