bgpreport

Network · data from 2026-11-12

AS55291 HARRIS-COUNTY-AS - Harris County

Registry name: HARRIS-COUNTY-AS - Harris County, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55291, 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.
162.216.48.0/22 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
74.124.60.0/24 No ROA Other IRR onlyNTTCOM 2 0%low visibility 2

AS-SET

AS55291 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 9 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none162.216.48.0/22No ROA covers it. Add a ROA for AS55291, maxLength 22.673 of 673
Route object: RIR162.216.48.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.124.60.0/24No ROA covers it. Add a ROA for AS55291, maxLength 24.2 of 673
Route object: RIR74.124.60.0/24Route object only in NTTCOM. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

162.216.48.0/24RADBNo ROA
162.216.49.0/24RADBNo ROA
162.216.50.0/23RADBNo ROA
162.216.50.0/24RADBNo ROA
162.216.51.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.