What is the nebius API's uptime?

Measured uptime for the nebius API averages 100% across 4 region(s) over the last 24 hours.

Is the nebius API down? Live status, latency & uptime by region

Last verified October 21, 2026 · rebuilt about every 30 minutes

Is the nebius API down right now?

Reachable from all 4 regions

Last successful probe Oct 21, 20:16 UTC · every 5 minutes from 4 region(s) · status feed checked Oct 21, 20:17 UTC

Every probe from every region reached the nebius API successfully in the last 72 hours. Measured from outside nebius’s own network, independently of its status page; full log: measured AI API incidents.

Real requests: not measured for nebius — only the API host is probed here, so errors limited to specific models are invisible to these probes. That is exactly what a status page tends to report, hence the line below.

nebius’s status page lists no open incident (checked Oct 21, 20:17 UTC).

As of October 21, 2026, the nebius AI API responds in 100 ms p50 (edge, time-to-first-byte) from Europe (Germany) — its fastest measured region — with 100% uptime. Slowest is Asia (Tokyo) at 475 ms p50.

Endpoint response (TTFB), 24 h

100 ms

Typical (p50) from Europe (Germany), the fastest region

Uptime, 24 h

100%

1,152 probes across 4 region(s)

Failed probes, 72 h

of 3,459 probes, all regions

Reported by nebius, 72 h

on status.nebius.com

Was nebius down in the last 3 days?

No. All 3,459 probes from 4 region(s) reached the nebius API in the last 72 hours.

Earlier days with nebius incidents: Oct 18 (status page) · Oct 16 (status page) · Oct 15 (status page) · Oct 14 (status page) · Oct 8 (status page) · Oct 7 (status page) · Oct 3 (status page) · Oct 2 (status page)

Show this live in your README: — embed code

What nebius’s own status page reported

Nothing. nebius’s status page lists no incident in the last 72 hours (checked Oct 21, 20:17 UTC).

Is nebius getting faster or slower?

Endpoint response (TTFB) · milliseconds · lower is faster

Last 72 hours · UTC · newest time on the right · current hour is incomplete.

Each line shows a region’s typical response per hour (p50), using the same scale. A gap means no successful timed probe in that hour.

typical response per hour (p50)all probes succeededsome failed (under half)half or more failedno probes recorded

Probe counts by region

Europe (Germany): 0 failed / 858 endpoint probesUS (Central): 0 failed / 856 endpoint probesAsia (Tokyo): 0 failed / 856 endpoint probesSouth America (São Paulo): 0 failed / 856 endpoint probes

Chart details

The strip shows endpoint probe outcomes, not model-request success. Adjacent hours with all successes or no data are joined. Hover an hour for its recorded values.

Latest is the most recent hourly p50 with data. Median is the median of hourly p50 values over these 72 hours. The “slower than usual” label means latest is at least 25% above that median; it is a relative change, not a fixed speed rating.

How fast is the nebius API from each region?

Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.

How to read these metrics

Endpoint response (TTFB)Network connection and the first response byte, without model inference.

Typical · p5050% of successful timed samples finish within this time.

Slower · p9595% of successful timed samples finish within this time.

Region	Typical (p50 TTFB)	Slower (p95)	Uptime
Asia (Tokyo)	475 ms	524 ms	100%
Europe (Germany)	100 ms	212 ms	100%
South America (São Paulo)	366 ms	375 ms	100%
US (Central)	179 ms	219 ms	100%

Measured from Europe (Germany), nebius responds in 100 ms; from Asia (Tokyo) the same API takes 475 ms — 4.8× longer for an identical request. That difference is the network path, not the model, and it applies to every call you make.

What is actually being measured here?

A probe in each region opens a real connection to nebius’s own API host every five minutes and times DNS resolution, the TCP handshake, the TLS handshake and the first byte of the response. Nothing is routed through a gateway or aggregator, so these figures describe nebius’s infrastructure rather than a reseller’s. Uptime counts a probe as failed only when the service genuinely fails — a 401 from an unauthenticated probe means the endpoint answered correctly and is counted as up.

What this page does not tell you

These are edge latency numbers: the time before the model begins generating. They say nothing about answer quality, throughput, price, or how long a full completion takes — those depend on the model you call. Edge latency matters because it is unavoidable: it is paid on every request, before a single token exists, and no prompt engineering removes it. Where an API key is available, inference time-to-first-token is measured separately and shown on the region pages with the model named next to the figure. Likewise, an unauthenticated probe cannot see errors that hit only some models or some accounts — the kind a status page usually reports — which is why nebius’s own reports are shown next to the measurements rather than folded into them.