Network · data from 2026-11-12
AS23614 KOCHI Network
Registry name: I-KOCHI - Kochi Systems Co., Ltd., JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23614, 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.254.164.0/22 | No ROA | Other IRR onlyJPIRR, NTTCOM | 668 99% |
| 210.158.184.0/21 | Valid | Other IRR onlyJPIRR, NTTCOM | 669 99% |
| 210.158.176.0/22 | Valid | Other IRR onlyJPIRR, NTTCOM | 667 99% |
| 210.158.181.0/24 | Valid | Other IRR onlyJPIRR, NTTCOM | 667 99% |
| 210.158.182.0/23 | Valid | Other IRR onlyJPIRR, NTTCOM | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS23614: AS-23614. 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 (AS23614 isn't in the set, or no route object for AS23614 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 | AS23614 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-23614 | In no IRR database read today. | |||||
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 8 are in fix.csv.
- ROA: none1
- Route object: RIR5
- AS-SET: not found1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.254.164.0/22 | No ROA covers it. Add a ROA for AS23614, maxLength 22. |
| Route object: RIR | 202.254.164.0/22 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 210.158.184.0/21 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 210.158.176.0/22 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 210.158.181.0/24 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 210.158.182.0/23 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| AS-SET: not found | AS-23614 | PeeringDB names AS-23614; no IRR database read has it. |
Route objects not announced
Route objects with origin AS23614 whose prefix no peer sees AS23614 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 210.158.176.0/20 | 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.