Network · data from 2026-11-12
AS211318 NEBIUS-UK Nebius B.V.
Registry name: NEBIUS-UK Nebius B.V., NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211318, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 87.58.0.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 2a13:5942:1020::/44 | No ROA | RIR databaseRIPE | 632 99% |
| 81.85.0.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 81.85.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.124.32.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 2a13:5942:420::/44 | Valid | RIR databaseRIPE | 633 100% |
| 2a13:5946:20::/44 | Valid | RIR databaseRIPE | 632 99% |
| 2a13:5947:136::/48 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS211318 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 3 are in fix.csv.
- ROA: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 87.58.0.0/20 | No ROA covers it. Add a ROA for AS211318, maxLength 20. |
| ROA: none | 2a13:5942:1020::/44 | No ROA covers it. Add a ROA for AS211318, maxLength 44. |
Route objects not announced
Route objects with origin AS211318 whose prefix no peer sees AS211318 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:5947:138::/48 | RIPE | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.