Network · data from 2026-11-12
AS398020 HICOUNTRYNET
Registry name: HICOUNTRYNET - HICOUNTRYNET, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS398020, 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.
| 209.142.76.0/24 | Valid | Nonecovered by 209.142.76.0/23 | 673 100% |
| 209.142.77.0/24 | Valid | Nonecovered by 209.142.76.0/23 | 673 100% |
| 2602:fde8::/44 | Valid | Nonecovered by 2602:fde8::/36 | 635 100% |
| 2602:fde8:10::/44 | Valid | Nonecovered by 2602:fde8::/36 | 635 100% |
| 23.133.48.0/24 | Valid | RIR databaseARIN | 673 100% |
| 23.133.49.0/24 | Valid | RIR databaseARIN | 673 100% |
| 66.205.243.0/24 | Valid | RIR databaseARIN | 673 100% |
| 174.136.212.0/22 | Valid | RIR databaseARIN | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS398020: ARIN::RS-HCN. 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 (AS398020 isn't in the set, or no route object for AS398020 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.
| Name | Database | ASNs | Sets | AS398020 in it | Not covered | |
|---|---|---|---|---|---|---|
| ARIN::RS-HCN | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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.
- Route object: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 209.142.76.0/24 | No route object for it. A route object for 209.142.76.0/23 with origin AS398020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398020 in the RIR database for the space. |
| Route object: none | 209.142.77.0/24 | No route object for it. A route object for 209.142.76.0/23 with origin AS398020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398020 in the RIR database for the space. |
| Route object: none | 2602:fde8::/44 | No route object for it. A route object for 2602:fde8::/36 with origin AS398020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398020 in the RIR database for the space. |
| Route object: none | 2602:fde8:10::/44 | No route object for it. A route object for 2602:fde8::/36 with origin AS398020 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398020 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS398020 whose prefix no peer sees AS398020 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 174.136.212.0/24 | ARIN | Valid |
| 174.136.213.0/24 | ARIN | Valid |
| 174.136.214.0/24 | ARIN | Valid |
| 174.136.215.0/24 | ARIN | Valid |
| 209.142.76.0/23 | ARIN | Valid |
| 2602:fde8::/32 | ARIN | Valid |
| 2602:fde8::/36 | ARIN | Valid |
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.