N
Outage recap · Nebius

Nebius outage — September 17, 2026

On September 17, 2026, Nebius had 2 reported incidents on Nebius's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Resuming IAM accounts is unavailable

none
Started
Sep 17, 6:46 AM EDT
Resolved
Sep 17, 7:45 AM EDT
Duration
58 min

Nebius's updates (3)

  1. investigating · Sep 17, 6:46 AM EDT

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

  2. monitoring · Sep 17, 7:10 AM EDT

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

  3. resolved · Sep 17, 7:45 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Nebius 11 times from Nebius's start time to its resolution, once every five minutes. Every one of them reached Nebius's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 180 ms, against 181 ms over the 24 hours before. Nebius posted the incident at Sep 17, 6:46 AM EDT.

Updates are Nebius's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

Compute services are partially unavailable for customers

major
Started
Sep 17, 12:26 PM EDT
Resolved
Sep 17, 1:09 PM EDT
Duration
43 min

Nebius's updates (2)

  1. investigating · Sep 17, 12:26 PM EDT

    We are currently experiencing a partial unavailability of our Compute services, which may affect some of your workloads. Our team is actively investigating the issue and working towards a resolution. We will provide further updates as soon as more information becomes available.

  2. resolved · Sep 17, 1:09 PM EDT

    The root cause was found and this incident has been resolved.

What our checks recorded

We checked Nebius 8 times from Nebius's start time to its resolution, once every five minutes. Every one of them reached Nebius's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 252 ms, against 192 ms over the 24 hours before. Nebius posted the incident at Sep 17, 12:26 PM EDT.

Updates are Nebius's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Nebius. This recap summarizes incidents published on Nebius's official status page.