Compute Cloud: some hosts unreachable in eu-north1
Some Compute Cloud hosts in eu-north1 became unreachable. The incident is resolved. It lasted 108 minutes.
State
Resolved
Started
Lasted
1 h 48 min
Worst impact
Partial outage
Timeline
4 updatesMonitoring
1 h 48 min 100%
Updates
Times in UTCAs posted by Nebius
The incident has been resolved
Some Compute Cloud hosts in eu-north1 became unreachable for 5 min, which may affect running virtual machines on them. Some hosts have since recovered, full recovery is not yet confirmed, and investigation is ongoing.
The affected Compute Cloud hosts in eu-north1 are reachable again, and no new unreachable hosts have been observed. We are verifying that virtual machines on the affected hosts have recovered, and the initial trigger is still under investigation.
Some Compute Cloud hosts in eu-north1 became unreachable for 5 min, which may affect running virtual machines on them. Some hosts have since recovered, full recovery is not yet confirmed, and investigation is ongoing.
Affected components
2Nebius in the last 90 days
Full historyIncidents in 90 days
30
Days with an incident
30
Median duration
1 h 38 min
This incident
About the median
Other Nebius incidents
All incidentsNebius·Network problems
Nebius reports a major outage that affects Token Factory and TF-CA1 - Token Factory. Nebius investigated the problem. The incident is resolved and it lasted about 8 hours and 13 minutes.
Nebius·Token Factory: some models unavailable in eu-north1
Nebius reports that some Token Factory models in eu-north1 did not work. The incident is resolved. It lasted about 36 minutes.
Nebius·Public API gateway partially unavailable in US-NORTH1 and US-CENTRAL1
The public API gateway and the Logging Service did not fully work in US-NORTH1 and US-CENTRAL1. Read requests to the Logging Service failed. Nebius reports that the incident is resolved, and it lasted 3 hours and 6 minutes.
Nebius·Token Factory: some dedicated endpoints partially unavailable
This incident has been resolved.
Nebius·Compute Cloud: disk images and snapshots partial unavailability
The incident has been resolved
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.
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.
https://outages.live/feed.xml?providers=nebius/feed subscribe https://outages.live/feed.xml?providers=nebiusFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane