Live

Connectivity issues for newly created worker nodes

This incident has been resolved.

The latest update from Nebius.

State

Resolved

Started

61 d ago

2026-09-01 16:11 UTC

Lasted

15 min

until 2026-09-01 16:26 UTC

Worst impact

Partial outage

Timeline

4 updates
16:1116:1516:1916:2216:26
Partial outageUpdate postedTimes in UTC

Identified

13 min 87%

Monitoring

2 min 13%

Updates

Times in UTC

As posted by Nebius

Resolved2026-09-01 16:26 UTC

This incident has been resolved.

Monitoring2026-09-01 16:25 UTC

We are continuing to monitor for any further issues.

Monitoring2026-09-01 16:24 UTC

The issue may have caused consequential impact to VPC functionality of VMs that are not Managed Service for Kubernetes worker nodes.

Identified2026-09-01 16:11 UTC

Worker nodes of Managed Service for Kubernetes clusters created after 15:13 CET Sep 1 2026 could experience problems connecting to/from other nodes in the same cluster. The root cause is understood and mitigation is underway.

Affected components

6
Virtual Private Cloud (Networking)Managed Service for Kubernetes®EU-NORTH1 - Virtual Private Cloud (Networking)EU-NORTH1 - Managed Service for Kubernetes®US-CENTRAL1 - Virtual Private Cloud (Networking)US-CENTRAL1 - Managed Service for Kubernetes®

Nebius in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

27

Median duration

1 h 18 min

This incident

81% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

24 h 33 min
median 1 h 18 min
90 days agoToday

Other Nebius incidents

All incidents

Follow Nebius

Your coding agent knows when Nebius is down, and tells you when a failure is theirs, not yours. You can also get Nebius incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "nebius" and tell me if Nebius has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=nebius
Slack
/feed subscribe https://outages.cc/feed.xml?providers=nebius

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane