Live

Compute Cloud: disk images and snapshots partial unavailability

The incident has been resolved

The latest update from Nebius.

State

Resolved

Started

5 d ago

2026-10-28 11:00 UTC

Lasted

6 h 55 min

until 2026-10-28 17:54 UTC

Worst impact

Partial outage

Timeline

7 updates
11:0012:4314:2716:1117:54
Partial outageUpdate postedTimes in UTC

Identified

6 h 39 min 96%

Monitoring

16 min 4%

Updates

Times in UTC

As posted by Nebius

Resolved2026-10-28 17:54 UTC

The incident has been resolved

Monitoring2026-10-28 17:38 UTC

The fix has been applied. Tasks are processed. We continue to monitor the accumulated queue and will consider incident resolved once the queue is processed.

Identified2026-10-28 13:49 UTC

We are continuing to work on a fix for this issue.

Identified2026-10-28 13:49 UTC

We are continuing to work on a fix for this issue.

Identified2026-10-28 13:47 UTC

We are continuing to work on a fix for this issue.

Identified2026-10-28 13:42 UTC

We are continuing to work on a fix for this issue.

Identified2026-10-28 11:00 UTC

Currently following operations are stuck or failing in some regions: - Creation of new images and snapshots - Creation of new disks from existing images and snapshots; - Creation of VM with managed disks with image or snapshot source - Hotplug of managed disk with image or snapshot source We have identified a loss of network connectivity to the eu-north2 region as the cause and are working to restore it.

Affected components

10
Compute CloudEU-NORTH1 - Compute CloudEU-NORTH2 - Compute CloudEU-WEST1 - Compute CloudUS-CENTRAL1 - Compute CloudME-WEST1 - Compute CloudUK-SOUTH1 - Compute CloudEU-WEST2 - Compute Cloud

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

5.3× 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.live/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.live/feed.xml?providers=nebius
Slack
/feed subscribe https://outages.live/feed.xml?providers=nebius

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane