Nebius

First posted only after it was over

16% 8 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Nebius: higher than most vendors.

Time to resolve

1 h 20 min median; 9 in 10 within 14 h 54 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Nebius: around the middle.

Major or critical incidents

4.3 a month 52 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Nebius: higher than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Nebius depends on

Runs in (named in its incidents): Google Cloud us-central1 (11), Google Cloud me-west1 (1).

Outage events: Google Cloud us-central1, Sep 1 (timing), Cloudflare, Nov 18, 2025 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full Nebius change history

No pricing, trust or legal pages tracked for Nebius.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Nebius incidents, last 90 daysJSONMarkdown