User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
nebius.com · AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 209 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1228 ms | 0 |
| Nov 7 | 0 | 0.0 | 67 ms | 0 |
| Nov 7 | 0 | 0.0 | 1234 ms | 0 |
| Nov 7 | 0 | 0.0 | 415 ms | 0 |
| Nov 7 | 0 | 0.0 | 121 ms | 0 |
| Nov 8 | 0 | 0.0 | 100 ms | 0 |
| Nov 8 | 0 | 0.0 | 730 ms | 0 |
| Nov 8 | 0 | 0.0 | 1179 ms | 0 |
| Nov 8 | 0 | 0.0 | 56 ms | 0 |
| Nov 9 | 0 | 0.0 | 921 ms | 0 |
| Nov 9 | 0 | 0.0 | 326 ms | 0 |
| Nov 9 | 0 | 0.0 | 91 ms | 0 |
| Nov 9 | 0 | 0.0 | 742 ms | 0 |
| Nov 10 | 0 | 0.0 | 201 ms | 0 |
| Nov 10 | 0 | 0.0 | 82 ms | 0 |
| Nov 10 | 0 | 0.0 | 576 ms | 0 |
| Nov 10 | 0 | 0.0 | 176 ms | 0 |
| Nov 11 | 0 | 0.0 | 1100 ms | 0 |
| Nov 11 | 0 | 0.0 | 659 ms | 0 |
| Nov 11 | 0 | 0.0 | 637 ms | 0 |
| Nov 11 | 0 | 0.0 | 478 ms | 0 |
| Nov 12 | 0 | 0.0 | 753 ms | 0 |
| Nov 12 | 0 | 0.0 | 718 ms | 0 |
| Nov 12 | 0 | 0.0 | 108 ms | 0 |
| Nov 12 | 0 | 0.0 | 166 ms | 0 |
| Nov 13 | 0 | 0.0 | 1080 ms | 0 |
| Nov 13 | 0 | 0.0 | 1275 ms | 0 |
| Nov 13 | 0 | 0.0 | 838 ms | 0 |
| Nov 13 | 0 | 0.0 | 209 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
One report per service every 10 minutes from this network. No account.
Get an email when Nebius goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nebius alerts to Slack, Discord or a webhook — free.
Nebius, at nebius.com, is one of the AI services we monitor. Build and scale faster on the purpose-built AI cloud, engineered from silicon to API.
Nebius publishes an official status page at status.nebius.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 835 ms average, 17–1477 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-06 and lasted 11 h 15 min. 1 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
835 ms on average over the last 24 hours (17–1477 ms).
Yes, at https://status.nebius.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Nebius here at once, the problem is on Nebius's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Nebius. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.