bgpreport

Network · data from 2026-11-12

AS32584 I-NETLINK - Xplore Inc.

Registry name: I-NETLINK - Xplore Inc., CA · not in PeeringDB

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

Announced routes

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

74.119.184.0/22 No ROA Nonecovered by 74.119.184.0/21 671 100% 68
74.119.188.0/22 No ROA Nonecovered by 74.119.184.0/21 671 100% 68
204.9.8.0/22 No ROA Nonecovered by 204.9.8.0/21 671 100% 68
204.9.12.0/22 No ROA Nonecovered by 204.9.8.0/21 671 100% 68
208.92.136.0/22 No ROA Nonecovered by 208.92.136.0/21 671 100% 68
208.92.140.0/22 No ROA Nonecovered by 208.92.136.0/21 671 100% 68
208.74.24.0/22 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

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

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none74.119.184.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: none74.119.184.0/22No route object for it. A route object for 74.119.184.0/21 with origin AS32584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32584 in the RIR database for the space.671 of 673
ROA: none74.119.188.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: none74.119.188.0/22No route object for it. A route object for 74.119.184.0/21 with origin AS32584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32584 in the RIR database for the space.671 of 673
ROA: none204.9.8.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: none204.9.8.0/22No route object for it. A route object for 204.9.8.0/21 with origin AS32584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32584 in the RIR database for the space.671 of 673
ROA: none204.9.12.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: none204.9.12.0/22No route object for it. A route object for 204.9.8.0/21 with origin AS32584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32584 in the RIR database for the space.671 of 673
ROA: none208.92.136.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: none208.92.136.0/22No route object for it. A route object for 208.92.136.0/21 with origin AS32584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32584 in the RIR database for the space.671 of 673
ROA: none208.92.140.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: none208.92.140.0/22No route object for it. A route object for 208.92.136.0/21 with origin AS32584 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32584 in the RIR database for the space.671 of 673
ROA: none208.74.24.0/22No ROA covers it. Add a ROA for AS32584, maxLength 22.671 of 673
Route object: RIR208.74.24.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

74.119.184.0/21RADBNo ROA
204.9.8.0/21RADBNo ROA
207.161.205.0/24BELLInvalid: origin
208.92.136.0/21RADBNo 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.