bgpreport

Network · data from 2026-11-12

AS23155 HTC-NET

Registry name: HTC-NET - HARRISONVILLE TELEPHONE, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23155, 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.114.96.0/20 No ROA Other IRR onlyRADB 669 99% 68
216.114.112.0/20 No ROA Other IRR onlyRADB 669 99% 68
65.87.40.0/21 Valid Nonecovered by 65.87.32.0/20 12 2%low visibility 11
65.87.48.0/21 Valid Nonecovered by 65.87.48.0/20 12 2%low visibility 11
65.87.32.0/20 Valid Other IRR onlyRADB 669 99% 68
65.87.48.0/20 Valid Other IRR onlyRADB 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS23155: ARIN::AS-HRVT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23155 isn't in the set, or no route object for AS23155 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS23155 in itNot covered
ARIN::AS-HRVT ARIN 010 No 6

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.

  • ROA: none2
  • Route object: none2
  • Route object: RIR4
  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none216.114.96.0/20No ROA covers it. Add a ROA for AS23155, maxLength 20.669 of 673
Route object: RIR216.114.96.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none216.114.112.0/20No ROA covers it. Add a ROA for AS23155, maxLength 20.669 of 673
Route object: RIR216.114.112.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: none65.87.40.0/21No route object for it. A route object for 65.87.32.0/20 with origin AS23155 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23155 in the RIR database for the space.12 of 673
Route object: none65.87.48.0/21No route object for it. A route object for 65.87.48.0/20 with origin AS23155 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23155 in the RIR database for the space.12 of 673
Route object: RIR65.87.32.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR65.87.48.0/20Route object only in RADB. Add it in the RIR database for the space.669 of 673
AS-SET: own ASNARIN::AS-HRVTAS23155 isn't in AS-HRVT (ARIN) once expanded. Add AS23155 to it.

Route objects not announced

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

65.87.32.0/19ARIN, RADBValid
216.114.96.0/19ARIN, RADBNo 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.