outages.live
Live
NebiusIncident · 2026-10-14 20:41 UTC

Connectivity issues between eu-south1 and other Nebius regions

ResolvedOfficial update

This incident has been resolved.

The latest update from Nebius.

State

Resolved

Started

18 d ago

2026-10-14 20:41 UTC

Lasted

9 h 9 min

until 2026-10-15 05:50 UTC

Worst impact

Degraded

Timeline

4 updates
20:4122:5801:1503:3305:50
DegradedUpdate postedTimes in UTC

Investigating

1 h 27 min 16%

Identified

7 h 43 min 84%

Updates

Times in UTC

As posted by Nebius

Resolved2026-10-15 05:50 UTC

This incident has been resolved.

Identified2026-10-14 22:08 UTC

We have identified the root cause of the connectivity issues and are preparing a fix. Currently, disk snapshot creation in NBS may be affected. Additionally, Nebius Console and API may experience higher latency than usual. We will provide further updates as we work to resolve the issue.

Identified2026-10-14 22:07 UTC

We have identified the root cause of the connectivity issues and are preparing a fix. Currently, disk snapshot creation in NBS may be affected. Additionally, Nebius Console and API may experience higher latency than usual. We will provide further updates as we work to resolve the issue.

Investigating2026-10-14 20:41 UTC

We are currently experiencing network connectivity issues between the eu-south1 region and other Nebius regions. Cross-region network traffic may be disrupted or experience degraded performance. Our team is investigating the issue and working to restore normal connectivity. We will provide updates as more information becomes available.

Affected components

6
Network Block StorageAPIManagement ConsoleEU-SOUTH1 - Network Block StorageEU-SOUTH1 - APIEU-SOUTH1 - Management Console

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

7.0× 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

Nebius·Token Factory: some dedicated endpoints partially unavailable

This incident has been resolved.

Resolvedresolved 2 d ago

Nebius·Compute Cloud: disk images and snapshots partial unavailability

The incident has been resolved

Resolvedresolved 4 d ago

Nebius·Token Factory 503 errors in eu-west2

The issue has been resolved.

Resolvedresolved 8 d ago

Nebius·Partial IAM and console unavailability

The console and IAM were unavailable for approximately 10 minutes. The incident has been mitigated, and service availability has been restored.

Resolvedresolved 14 d ago

Nebius·CLI login issues

This incident has been resolved.

Resolvedresolved 16 d ago

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