bgpreport

Network · data from 2026-11-12

AS210560 Nebius Israel Ltd

Registry name: NEBIUSISRAEL Nebius Israel Ltd, IL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210560, 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.
89.124.40.0/22 No ROA RIR databaseRIPE 673 100% 67
46.243.144.0/22 Valid RIR databaseRIPE 673 100% 67
2a11:f740:20::/44 Valid RIR databaseRIPE 634 100% 68
2a13:5947:135::/48 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS210560's PeeringDB record names no 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 11 are in fix.csv.

  • ROA: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none89.124.40.0/22No ROA covers it. Add a ROA for AS210560, maxLength 22.673 of 673

Route objects not announced

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

46.243.144.0/23RIPEInvalid: maxLength
46.243.144.0/24RIPEInvalid: maxLength
46.243.145.0/24RIPEInvalid: maxLength
46.243.146.0/23RIPEValid
46.243.146.0/24RIPEValid
66.201.30.0/24RIPENo ROA
2001:8f8:d002::/48RIPEInvalid: origin
2a11:f740::/48RIPENo ROA
2a11:f740:1::/48RIPENo ROA
2a11:f740:2::/48RIPEValid

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.