bgpreport

Network · data from 2026-11-12

AS19927 NHMCCD - Lone Star College System District

Registry name: NHMCCD - Lone Star College System District, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19927, 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.
69.41.31.0/24 No ROA Nonecovered by 69.41.16.0/20 671 100% 67
216.7.252.0/24 No ROA Nonecovered by 216.7.252.0/22 671 100% 67
216.7.253.0/24 No ROA Nonecovered by 216.7.252.0/22 671 100% 67
69.41.28.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.7.224.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
216.7.224.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.7.225.0/24 No ROA Other IRR onlyRADB 673 100% 67
69.41.29.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
192.251.1.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
192.251.2.0/24 No ROA Other IRR onlyNTTCOM 671 100% 67
216.7.252.0/22 No ROA Other IRR onlyNTTCOM 671 100% 67

AS-SET

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

  • ROA: none11
  • Route object: none3
  • Route object: RIR8
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none69.41.31.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.671 of 673
Route object: none69.41.31.0/24No route object for it. A route object for 69.41.16.0/20 with origin AS19927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19927 in the RIR database for the space.671 of 673
ROA: none216.7.252.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.671 of 673
Route object: none216.7.252.0/24No route object for it. A route object for 216.7.252.0/22 with origin AS19927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19927 in the RIR database for the space.671 of 673
ROA: none216.7.253.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.671 of 673
Route object: none216.7.253.0/24No route object for it. A route object for 216.7.252.0/22 with origin AS19927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19927 in the RIR database for the space.671 of 673
ROA: none69.41.28.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.673 of 673
Route object: RIR69.41.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.7.224.0/22No ROA covers it. Add a ROA for AS19927, maxLength 22.673 of 673
Route object: RIR216.7.224.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.7.224.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.673 of 673
Route object: RIR216.7.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.7.225.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.673 of 673
Route object: RIR216.7.225.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none69.41.29.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.671 of 673
Route object: RIR69.41.29.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none192.251.1.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.671 of 673
Route object: RIR192.251.1.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none192.251.2.0/24No ROA covers it. Add a ROA for AS19927, maxLength 24.671 of 673
Route object: RIR192.251.2.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
ROA: none216.7.252.0/22No ROA covers it. Add a ROA for AS19927, maxLength 22.671 of 673
Route object: RIR216.7.252.0/22Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

69.41.16.0/20NTTCOM, RADBNo ROA
69.41.16.0/24RADBNo ROA
69.41.17.0/24NTTCOM, RADBNo ROA
69.41.18.0/23RADBNo ROA
69.41.18.0/24NTTCOM, RADBNo ROA
69.41.19.0/24RADBNo ROA
69.41.20.0/22RADBNo ROA
69.41.20.0/24NTTCOMNo ROA
69.41.21.0/24NTTCOM, RADBNo ROA
69.41.22.0/24NTTCOMNo ROA
69.41.23.0/24NTTCOMNo ROA
216.7.224.0/19NTTCOM, RADBNo ROA
216.7.226.0/24RADBNo ROA
216.7.227.0/24RADBNo ROA
216.7.228.0/22NTTCOM, RADBNo ROA
216.7.228.0/24RADBNo ROA
216.7.229.0/24RADBNo ROA
216.7.230.0/24RADBNo ROA
216.7.231.0/24RADBNo 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.