Nebius lists these components: Token Factory, TF-CA1 - Token Factory.

When did the incident start and end?

It started at 2026-11-06 19:31 UTC. This page shows the end time when Nebius marks it resolved.

How do I get alerts for Nebius?

Subscribe to the Nebius live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Nebius. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

NebiusIncident ·

Network problems

Q: What happened?

Nebius reported "Network problems" on its status page at 2026-11-06 19:31 UTC. Nebius reports a major network outage that affects Token Factory and TF-CA1 - Token Factory. Nebius is investigating the issue.

Major outageOfficial update

Nebius reports a major network outage that affects Token Factory and TF-CA1 - Token Factory. Nebius is investigating the issue.

State

Investigating

Started

Ongoing for

1 h 59 min

Worst impact

Major outage

Timeline

3 updates

19:3120:0120:3121:0021:30

Major outageNoticeUpdate postedTimes in UTC

Investigating

1 h 56 min 97%

Resolved

3 min 3%

Updates

Times in UTC

As posted by Nebius

Investigating

We are currently investigating this issue.

Resolved

Investigating

We are currently investigating this issue.

Affected components

Token FactoryTF-CA1 - Token Factory

Nebius in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 16 min

This incident

1.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 16 min

90 days agoToday

Other Nebius incidents

All incidents

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.

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. Read requests to the Logging Service failed. Nebius reports that the incident is resolved, and it lasted 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.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