Network · data from 2026-11-12
AS7668 HTCN
Registry name: HTCN - Hokuriku Telecommunication Network Co., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7668, 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.
| 202.242.34.0/24 | No ROA | Other IRR onlyJPIRR, RADB | 671 100% |
| 202.213.96.0/19 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 211.120.192.0/20 | Valid | Other IRR onlyJPIRR, RADB | 673 100% |
| 210.167.0.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 210.250.160.0/19 | Valid | Other IRR onlyJPIRR, RADB | 672 100% |
| 202.245.196.0/23 | Valid | Other IRR onlyJPIRR, RADB | 671 100% |
| 210.166.5.0/24 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 210.250.191.0/24 | Valid | Other IRR onlyJPIRR, RADB | 670 100% |
| 210.250.190.0/24 | Valid | Other IRR onlyJPIRR | 667 99% |
| 2001:308::/32 | Valid | Other IRR onlyJPIRR, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS7668: AS-HTCN. 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 (AS7668 isn't in the set, or no route object for AS7668 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 | AS7668 in it | Not covered |
|---|---|---|---|---|---|
| AS-HTCN | RADB | 6 | 1 | Yes | 0 |
| JPIRR (also) | 6 | 1 | 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.
- ROA: none1
- Route object: RIR10
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.242.34.0/24 | No ROA covers it. Add a ROA for AS7668, maxLength 24. |
| Route object: RIR | 202.242.34.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.213.96.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 211.120.192.0/20 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.167.0.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.250.160.0/19 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.245.196.0/23 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.166.5.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.250.191.0/24 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 210.250.190.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2001:308::/32 | Route object only in JPIRR, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7668 whose prefix no peer sees AS7668 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.245.12.0/24 | RADB | No 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.