Network · data from 2026-11-12
AS4697 NTT NTLab
Registry name: NTTV6NET - Nippon Telegraph and Telephone Corporation, JP · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4697, 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.
| 192.16.178.0/24 | No ROA | Other IRR onlyJPIRR | 671 100% |
| 192.26.93.0/24 | No ROA | Other IRR onlyJPIRR, NTTCOM | 671 100% |
| 192.47.162.0/23 | No ROA | Other IRR onlyJPIRR, NTTCOM | 671 100% |
| 192.47.164.0/23 | No ROA | Other IRR onlyJPIRR, NTTCOM | 671 100% |
| 192.47.174.0/23 | No ROA | Other IRR onlyJPIRR | 671 100% |
| 192.47.176.0/22 | No ROA | Other IRR onlyJPIRR | 671 100% |
| 192.172.237.0/24 | No ROA | Other IRR onlyJPIRR, NTTCOM | 671 100% |
| 2001:fa8::/32 | No ROA | Other IRR onlyJPIRR, NTTCOM | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS4697: JPIRR::AS4697. 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 (AS4697 isn't in the set, or no route object for AS4697 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 | AS4697 in it | Not covered | |
|---|---|---|---|---|---|---|
| JPIRR::AS4697 | A single AS number, not a set: AS4697 (this network), 8 route objects. | |||||
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 16 are in fix.csv.
- ROA: none8
- Route object: RIR8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.16.178.0/24 | No ROA covers it. Add a ROA for AS4697, maxLength 24. |
| Route object: RIR | 192.16.178.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 192.26.93.0/24 | No ROA covers it. Add a ROA for AS4697, maxLength 24. |
| Route object: RIR | 192.26.93.0/24 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 192.47.162.0/23 | No ROA covers it. Add a ROA for AS4697, maxLength 23. |
| Route object: RIR | 192.47.162.0/23 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 192.47.164.0/23 | No ROA covers it. Add a ROA for AS4697, maxLength 23. |
| Route object: RIR | 192.47.164.0/23 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 192.47.174.0/23 | No ROA covers it. Add a ROA for AS4697, maxLength 23. |
| Route object: RIR | 192.47.174.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 192.47.176.0/22 | No ROA covers it. Add a ROA for AS4697, maxLength 22. |
| Route object: RIR | 192.47.176.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| ROA: none | 192.172.237.0/24 | No ROA covers it. Add a ROA for AS4697, maxLength 24. |
| Route object: RIR | 192.172.237.0/24 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 2001:fa8::/32 | No ROA covers it. Add a ROA for AS4697, maxLength 32. |
| Route object: RIR | 2001:fa8::/32 | Route object only in JPIRR, NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS4697 is announced.
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.