bgpreport

Network · data from 2026-11-12

AS30167 XCNETWORKS-30167 - XC Networks, Ltd.

Registry name: XCNETWORKS-30167 - XC Networks, Ltd., US · not in PeeringDB

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

Announced routes

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

216.171.64.0/19 No ROA Other origin only 673 100% 67
216.171.90.0/24 No ROA None 673 100% 67
216.171.93.0/24 No ROA None 673 100% 67
64.68.211.0/24 No ROA Other origin only 671 100% 67
64.68.216.0/24 No ROA Other origin only 671 100% 67
64.68.219.0/24 No ROA None 671 100% 67
216.171.71.0/24 No ROA None 671 100% 67
64.68.210.0/24 No ROA Other origin only 670 100% 67
201.174.30.0/24 Valid Other origin onlycovered by 201.174.30.0/23 673 100% 67
201.174.31.0/24 Valid Other origin onlycovered by 201.174.30.0/23 671 100% 67
201.174.43.0/24 Valid RIR databaseLACNIC 671 100% 67
201.174.44.0/24 Valid RIR databaseLACNIC 671 100% 67

AS-SET

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

  • ROA: none8
  • Route object: none10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none216.171.64.0/19No ROA covers it. Add a ROA for AS30167, maxLength 19.673 of 673
Route object: none216.171.64.0/19Route objects for it name AS32098. Add a route object with origin AS30167 in the RIR database for the space.673 of 673
ROA: none216.171.90.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.673 of 673
Route object: none216.171.90.0/24No route object for it. Add a route object with origin AS30167 in the RIR database for the space.673 of 673
ROA: none216.171.93.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.673 of 673
Route object: none216.171.93.0/24No route object for it. Add a route object with origin AS30167 in the RIR database for the space.673 of 673
ROA: none64.68.211.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.671 of 673
Route object: none64.68.211.0/24Route objects for it name AS32098. Add a route object with origin AS30167 in the RIR database for the space.671 of 673
ROA: none64.68.216.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.671 of 673
Route object: none64.68.216.0/24Route objects for it name AS32098. Add a route object with origin AS30167 in the RIR database for the space.671 of 673
ROA: none64.68.219.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.671 of 673
Route object: none64.68.219.0/24No route object for it. Add a route object with origin AS30167 in the RIR database for the space.671 of 673
ROA: none216.171.71.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.671 of 673
Route object: none216.171.71.0/24No route object for it. Add a route object with origin AS30167 in the RIR database for the space.671 of 673
ROA: none64.68.210.0/24No ROA covers it. Add a ROA for AS30167, maxLength 24.670 of 673
Route object: none64.68.210.0/24Route objects for it name AS32098. Add a route object with origin AS30167 in the RIR database for the space.670 of 673
Route object: none201.174.30.0/24Route objects for it name AS32098. A route object for 201.174.30.0/23 with origin AS30167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30167 in the RIR database for the space.673 of 673
Route object: none201.174.31.0/24Route objects for it name AS32098. A route object for 201.174.30.0/23 with origin AS30167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30167 in the RIR database for the space.671 of 673

Route objects not announced

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

201.174.30.0/23LACNICValid
201.174.100.0/24LACNIC, RADBValid
201.174.106.0/24LACNICValid
201.174.245.0/24LACNICValid

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.