outages.live
Live
NebiusIncident · 2026-08-05 14:27 UTC

Creation of new VMs is broken

ResolvedOfficial update

This incident has been resolved.

The latest update from Nebius.

State

Resolved

Started

88 d ago

2026-08-05 14:27 UTC

Lasted

1 h 18 min

until 2026-08-05 15:45 UTC

Worst impact

Notice

Timeline

4 updates
14:2714:4615:0615:2615:45
NoticeUpdate postedTimes in UTC

Investigating

16 min 21%

Monitoring

1 h 2 min 79%

Updates

Times in UTC

As posted by Nebius

Resolved2026-08-05 15:45 UTC

This incident has been resolved.

Monitoring2026-08-05 14:43 UTC

A fix has been implemented and we are monitoring the results.

Investigating2026-08-05 14:29 UTC

We are continuing to investigate this issue.

Investigating2026-08-05 14:27 UTC

Due to issue with internal services the creation of new VM and other operations may be affected. We are investigating the issue.

Affected components

3
Compute CloudEU-WEST1 - Compute CloudUK-SOUTH1 - Compute Cloud

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