Who is down right now

Nebius · AIOct 4, 2026, 15:54 UTC 6 days ago

Issues with preempted Managed Kubernetes nodes in all regions

MinorNot disclosedUpdated 2h ago
Oct 4, 15:54 UTCOct 5, 15:54 UTC
Duration
24h
Impact
Minor
Root cause
Not disclosed
Nebius, 90 days
22 incidents
Affected
Managed Service for Kubernetes®EU-NORTH1 - Managed Service for Kubernetes®EU-NORTH2 - Managed Service for Kubernetes®EU-WEST1 - Managed Service for Kubernetes®US-CENTRAL1 - Managed Service for Kubernetes®ME-WEST1 - Managed Service for Kubernetes®UK-SOUTH1 - Managed Service for Kubernetes®EU-WEST2 - Managed Service for Kubernetes®US-NORTH1 - Managed Service for Kubernetes®EU-SOUTH1 - Managed Service for Kubernetes®
Status page

Final update

This incident has been resolved.

Timeline

  1. Resolved · Oct 5, 15:54 UTC
    This incident has been resolved.
  2. Identified · Oct 2, 15:50 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. Investigating · Oct 2, 15:31 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.

More from Nebius

Full history