bgpreport

Network · data from 2026-11-12

AS20650 IP NEXIA

Registry name: IPNEXIA-AS IP NEXIA N.V., BE · PeeringDB

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

Announced routes

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

217.145.42.0/24 Valid Nonecovered by 217.145.32.0/20 673 100% 66
217.145.46.0/24 Valid Nonecovered by 217.145.32.0/20 673 100% 66
77.72.232.0/24 Valid Nonecovered by 77.72.232.0/21 672 100% 66
77.72.234.0/24 Valid Nonecovered by 77.72.232.0/21 672 100% 66
77.72.236.0/24 Valid Nonecovered by 77.72.232.0/21 672 100% 66
217.145.32.0/23 Valid RIR databaseRIPE 673 100% 66
217.145.34.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.35.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.36.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.37.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.38.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.39.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.40.0/23 Valid RIR databaseRIPE 673 100% 66
217.145.43.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.44.0/24 Valid RIR databaseRIPE 673 100% 66
217.145.45.0/24 Valid RIR databaseRIPE 673 100% 66
77.72.237.0/24 Valid RIR databaseRIPE 672 100% 66
77.72.238.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS20650'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.

  • Route object: none5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none217.145.42.0/24No route object for it. A route object for 217.145.32.0/20 with origin AS20650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20650 in the RIR database for the space.673 of 673
Route object: none217.145.46.0/24No route object for it. A route object for 217.145.32.0/20 with origin AS20650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20650 in the RIR database for the space.673 of 673
Route object: none77.72.232.0/24No route object for it. A route object for 77.72.232.0/21 with origin AS20650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20650 in the RIR database for the space.672 of 673
Route object: none77.72.234.0/24No route object for it. A route object for 77.72.232.0/21 with origin AS20650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20650 in the RIR database for the space.672 of 673
Route object: none77.72.236.0/24No route object for it. A route object for 77.72.232.0/21 with origin AS20650 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20650 in the RIR database for the space.672 of 673

Route objects not announced

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

77.72.232.0/21RIPEValid
77.72.239.0/24RIPEValid
217.145.32.0/20RIPEValid
217.145.32.0/24RIPEValid
217.145.33.0/24RIPEValid
2a01:38::/32RIPEValid

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.