Live

Issues logging to the Management Console

Some newly registered users may have experienced issues logging in to the management console between 13:00 UTC on 17 August 2026 and 14:00 UTC on 18 August 2026.

The latest update from Nebius.

State

Resolved

Started

77 d ago

2026-08-17 13:00 UTC

Lasted

1 min

until 2026-08-17 13:00 UTC

Worst impact

Degraded

Timeline

1 update
13:0013:0013:0013:0013:01
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Nebius

Resolved2026-08-17 13:00 UTC

Some newly registered users may have experienced issues logging in to the management console between 13:00 UTC on 17 August 2026 and 14:00 UTC on 18 August 2026.

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

100% shorter than 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