outages.live
Live
NebiusIncident ·

Network problems

ResolvedOfficial update
0

Nebius reports network problems that affect Token Factory and TF-CA1 - Token Factory. The incident is resolved. It lasted 8 hours and 13 minutes.

State

Resolved

Started

Lasted

8 h 13 min

Worst impact

Major outage

Timeline

4 updates
19:3121:3423:3701:4003:44
Major outageNoticeUpdate postedTimes in UTC

Investigating

8 h 10 min 99%

Resolved

3 min 1%

Updates

Times in UTC

As posted by Nebius

Resolved

This incident has been resolved.

Investigating

We are currently investigating this issue.

Resolved
Investigating

We are currently investigating this issue.

Affected components

2
Token FactoryTF-CA1 - Token Factory

Nebius in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

29

Days with an incident

30

Median duration

1 h 29 min

This incident

5.6× 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 29 min
90 days agoToday

Other Nebius incidents

All incidents

Nebius·Token Factory: some models unavailable in eu-north1

Some Token Factory models did not work in eu-north1. Nebius reports that the incident is resolved. The outage lasted 36 minutes.

Resolved

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. Nebius reports that the incident is resolved. It lasted about 3 hours and 6 minutes.

Resolved

Nebius·Token Factory: some dedicated endpoints partially unavailable

This incident has been resolved.

Resolved

Nebius·Compute Cloud: disk images and snapshots partial unavailability

The incident has been resolved

Resolved

Nebius·Token Factory 503 errors in eu-west2

The issue has been resolved.

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.

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