Nebius reported "Resuming IAM accounts is unavailable" on its status page at 2026-09-17 10:46 UTC.

When did the incident start and end?

It started at 2026-09-17 10:46 UTC and ended at 2026-09-17 11:45 UTC. It lasted 58 min.

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.

NebiusIncident · 2026-09-17 10:46 UTC

Resuming IAM accounts is unavailable

Q: What is affected?

Nebius lists these components: Identity and Access Management, EU-NORTH1 - Identity and Access Management, US-CENTRAL1 - Identity and Access Management.

ResolvedOfficial update

This incident has been resolved.

The latest update from Nebius.

State

Resolved

Started

46 d ago

2026-09-17 10:46 UTC

Lasted

58 min

until 2026-09-17 11:45 UTC

Worst impact

Notice

Timeline

3 updates

10:4611:0111:1611:3011:45

NoticeUpdate postedTimes in UTC

Investigating

24 min 41%

Monitoring

34 min 59%

Updates

Times in UTC

As posted by Nebius

Resolved2026-09-17 11:45 UTC

This incident has been resolved.

Monitoring2026-09-17 11:10 UTC

Root cause is located and fixed. We keep monitoring the resolution.

Investigating2026-09-17 10:46 UTC

We are investigating an issue with IAM Tenants Status change. Customers may not be able to resume their accounts from the suspended state.

Affected components

Identity and Access ManagementEU-NORTH1 - Identity and Access ManagementUS-CENTRAL1 - Identity and Access Management

Nebius in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 18 min

This incident

25% 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

Nebius·Token Factory: some dedicated endpoints partially unavailable

This incident has been resolved.

Resolvedresolved 2 d ago

Nebius·Compute Cloud: disk images and snapshots partial unavailability

The incident has been resolved

Resolvedresolved 4 d ago

Nebius·Token Factory 503 errors in eu-west2

The issue has been resolved.

Resolvedresolved 9 d ago

Nebius·Partial IAM and console unavailability

The console and IAM were unavailable for approximately 10 minutes. The incident has been mitigated, and service availability has been restored.

Resolvedresolved 15 d ago

Nebius·CLI login issues

This incident has been resolved.

Resolvedresolved 17 d ago

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