N
Outage recap · Nebius

Nebius outage — September 16, 2026

On September 16, 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.

[us-central1] Object Storage is partially unavailable

major
Started
Sep 16, 6:45 AM EDT
Resolved
Sep 16, 11:42 AM EDT
Duration
4h 57m

Nebius's updates (3)

  1. investigating · Sep 16, 6:45 AM EDT

    Users might be experiencing a high rate of 5xx errors on upload requests and elevated latency on read requests.

  2. identified · Sep 16, 11:12 AM EDT

    The team has identified the root cause of the issue and is currently applying a fix. We expect the incident to be fully mitigated within two hours.

  3. resolved · Sep 16, 11:42 AM EDT

    This incident has been resolved.

What our checks recorded

We checked Nebius 60 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 158 ms, against 196 ms over the 24 hours before. Nebius posted the incident at Sep 16, 6:45 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 ↗

[eu-west1] Metrics for resources in this region are partially unavailable

major
Started
Sep 16, 12:52 PM EDT
Resolved
Sep 16, 2:21 PM EDT
Duration
1h 29m

Nebius's updates (2)

  1. investigating · Sep 16, 12:52 PM EDT

    We are currently investigating this issue.

  2. resolved · Sep 16, 2:21 PM EDT

    This incident has been resolved.

What our checks recorded

We checked Nebius 18 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 162 ms, against 183 ms over the 24 hours before. Nebius posted the incident at Sep 16, 12:52 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.