bgpreport

Network · data from 2026-11-12

AS214415 NebiusPA10 Nebius B.V.

Registry name: NebiusPA10 Nebius B.V., NL · not in PeeringDB

9IPv4 routes 66.7% RPKI valid · 77.8% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS214415, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS214415, 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.

66.201.1.0/24 No ROA RIR databaseRIPE 673 100% 67
66.201.2.0/24 No ROA RIR databaseRIPE 673 100% 67
66.201.4.0/22 No ROA RIR databaseRIPE 673 100% 67
185.175.110.0/24 Valid Nonecovered by 185.175.110.0/23 673 100% 67
185.175.111.0/24 Valid Nonecovered by 185.175.110.0/23 673 100% 67
185.175.108.0/24 Valid RIR databaseRIPE 673 100% 67
185.175.109.0/24 Valid RIR databaseRIPE 673 100% 67
213.239.160.0/21 Valid RIR databaseRIPE 673 100% 67
213.239.168.0/21 Valid RIR databaseRIPE 673 100% 67
2a13:5944:20::/44 Valid RIR databaseRIPE 633 100% 67
2a13:5947:134::/48 Valid RIR databaseRIPE 633 100% 67
2a13:5940:120::/44 Valid RIR databaseRIPE 632 99% 68
2a13:5947:137::/48 Valid RIR databaseRIPE 632 99% 68

AS-SET

AS214415 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 7 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none66.201.1.0/24No ROA covers it. Add a ROA for AS214415, maxLength 24.673 of 673
ROA: none66.201.2.0/24No ROA covers it. Add a ROA for AS214415, maxLength 24.673 of 673
ROA: none66.201.4.0/22No ROA covers it. Add a ROA for AS214415, maxLength 22.673 of 673
Route object: none185.175.110.0/24No route object for it. A route object for 185.175.110.0/23 with origin AS214415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214415 in the RIR database for the space.673 of 673
Route object: none185.175.111.0/24No route object for it. A route object for 185.175.110.0/23 with origin AS214415 covers it (filters allowing more-specifics accept it). Add a route object with origin AS214415 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS214415 whose prefix no peer sees AS214415 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.175.110.0/23RIPENo ROA
195.242.6.0/24RIPENo 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.