bgpreport

Network · data from 2026-11-12

AS36813 Hamilton County Communications, Inc

Registry name: HCC-IL - Hamilton County Communications, Inc, US · PeeringDB

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

Announced routes

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

64.127.84.0/22 Valid Nonecovered by 64.127.80.0/20 671 100% 68
64.127.88.0/22 Valid Nonecovered by 64.127.80.0/20 671 100% 68
64.127.92.0/22 Valid Nonecovered by 64.127.80.0/20 671 100% 68
66.220.84.0/22 Valid Nonecovered by 66.220.80.0/20 671 100% 68
139.60.80.0/22 Valid Nonecovered by 139.60.80.0/20 671 100% 68
2606:2c80::/38 Valid Nonecovered by 2606:2c80::/32 634 100% 69
2606:2c80:3::/48 Valid Nonecovered by 2606:2c80::/32 634 100% 69
2606:2c80:4::/48 Valid Nonecovered by 2606:2c80::/32 634 100% 69
2606:2c80:2f::/48 Valid Nonecovered by 2606:2c80::/32 634 100% 69
64.127.80.0/22 Valid Nonecovered by 64.127.80.0/20 3 0%low visibility 3
64.127.80.0/20 Valid RIR databaseARIN 671 100% 68
66.220.80.0/20 Valid RIR databaseARIN 671 100% 68
139.60.80.0/20 Valid RIR databaseARIN 671 100% 68
2606:2c80::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS36813: ARIN::AS-HMCM. 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 (AS36813 isn't in the set, or no route object for AS36813 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 objectsAS36813 in itNot covered
ARIN::AS-HMCM ARIN 217 Yes 0

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

  • Route object: none10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none64.127.84.0/22No route object for it. A route object for 64.127.80.0/20 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.671 of 673
Route object: none64.127.88.0/22No route object for it. A route object for 64.127.80.0/20 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.671 of 673
Route object: none64.127.92.0/22No route object for it. A route object for 64.127.80.0/20 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.671 of 673
Route object: none66.220.84.0/22No route object for it. A route object for 66.220.80.0/20 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.671 of 673
Route object: none139.60.80.0/22No route object for it. A route object for 139.60.80.0/20 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.671 of 673
Route object: none2606:2c80::/38No route object for it. A route object for 2606:2c80::/32 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.634 of 636
Route object: none2606:2c80:3::/48No route object for it. A route object for 2606:2c80::/32 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.634 of 636
Route object: none2606:2c80:4::/48No route object for it. A route object for 2606:2c80::/32 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.634 of 636
Route object: none2606:2c80:2f::/48No route object for it. A route object for 2606:2c80::/32 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.634 of 636
Route object: none64.127.80.0/22No route object for it. A route object for 64.127.80.0/20 with origin AS36813 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36813 in the RIR database for the space.3 of 673

Route objects not announced

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

64.127.90.0/23ARINValid
104.37.68.0/22RADBNo 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.