Announced routes
Every prefix a peer of the route collectors sees with origin AS16970, 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.
| 23.169.240.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.241.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.242.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.243.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.244.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.245.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.248.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.249.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.250.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.251.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.252.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.253.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.254.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 23.169.255.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 64.40.23.0/24 | Valid | Other IRR onlyNTTCOM | 671 100% |
| 72.20.158.0/24 | Valid | Other IRR onlyNTTCOM | 670 100% |
| 2602:800:1000::/44 | Valid | Other IRR onlyNTTCOM | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS16970: NTTCOM::AS16970:AS-MIDNET-ALL. 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 (AS16970 isn't in the set, or no route object for AS16970 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 | AS16970 in it | Not covered |
|---|---|---|---|---|---|
| NTTCOM::AS16970:AS-MIDNET-ALL | NTTCOM2 member sets in no database: AS-LAKESIDE, AS401414:AS-ALL | 4 | 4 | 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 19 are in fix.csv.
- Route object: RIR17
- AS-SET: missing member2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 23.169.240.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.241.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.242.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.243.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.244.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.245.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.248.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.249.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.250.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.251.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.252.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.253.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.254.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 23.169.255.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 64.40.23.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 72.20.158.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2602:800:1000::/44 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| AS-SET: missing member | NTTCOM::AS16970:AS-MIDNET-ALL | AS16970:AS-MIDNET-ALL (NTTCOM) lists AS-LAKESIDE; no IRR database read has it. |
| AS-SET: missing member | NTTCOM::AS16970:AS-MIDNET-ALL | AS16970:AS-MIDNET-ALL (NTTCOM) lists AS401414:AS-ALL; no IRR database read has it. |
Route objects not announced
Every route object with origin AS16970 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.