Live / Nebius / Incident
Nebius: Connectivity issues between eu-south1 and other Nebius regions
Nebius · nebius.comMinor incidentResolved2026-10-15 05:50 UTC
Public — what happened
Summary
Nebius reported a minor incident starting at 20:41 UTC on 2026-10-14 in which network links between its eu-south1 region and its other regions were disrupted, potentially slowing or interrupting traffic moving between regions. At 22:07 UTC the company said it had found the underlying cause, without describing it, and was working on a fix; it added that creating disk snapshots in NBS might not work properly and that the Nebius Console and API could respond more slowly than normal. The incident was marked resolved on 2026-10-15 at 05:50.
Affected
Network Block Storage, API, Management Console
Timeline
- Started — 2026-10-14 20:41 UTC
- Investigating — 2026-10-14 20:41 UTC
- Identified — 2026-10-14 22:07 UTC (2 updates)
- Resolved — 2026-10-15 05:50 UTC · 9h 09m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Nebius against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Nebius: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Nebius report →
More from Nebius
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.