Network · data from 2026-11-12
AS17975 APT-AP - AS # for peering purpose with IX and ISP.
Registry name: APT-AP - AS # for peering purpose with IX and ISP., HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17975, 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.
| 221.120.183.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.169.32.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 203.169.33.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 203.169.35.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 203.169.47.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 221.120.179.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 221.120.180.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 203.169.46.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.176.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.177.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.184.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.185.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.186.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.187.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 221.120.189.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.169.34.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
AS-SET
AS17975 isn't in PeeringDB, where networks name their AS-SET.
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 110 are in fix.csv.
- ROA: none16
- Route object: RIR15
- Route object: not announced79
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 221.120.183.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.183.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.169.32.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 203.169.32.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.169.33.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 203.169.33.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.169.35.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 203.169.35.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.169.47.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 203.169.47.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.179.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.179.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.180.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.180.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.169.46.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 203.169.46.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.176.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.176.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.177.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.177.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.184.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.184.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.185.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.185.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.186.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.186.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.187.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.187.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 221.120.189.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
| Route object: RIR | 221.120.189.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.169.34.0/24 | No ROA covers it. Add a ROA for AS17975, maxLength 24. |
Route objects not announced
Route objects with origin AS17975 whose prefix no peer sees AS17975 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 116.206.27.0/24 | NTTCOM, RADB | No ROA |
| 203.80.177.0/24 | NTTCOM, RADB | No ROA |
| 203.169.32.0/20 | APNIC, NTTCOM, RADB | No ROA |
| 203.169.32.0/21 | NTTCOM, RADB | No ROA |
| 203.169.32.0/22 | NTTCOM, RADB | No ROA |
| 203.169.32.0/23 | NTTCOM, RADB | No ROA |
| 203.169.34.0/23 | NTTCOM, RADB | No ROA |
| 203.169.36.0/22 | NTTCOM, RADB | No ROA |
| 203.169.36.0/23 | NTTCOM, RADB | No ROA |
| 203.169.36.0/24 | NTTCOM, RADB | No ROA |
| 203.169.37.0/24 | NTTCOM, RADB | No ROA |
| 203.169.38.0/23 | NTTCOM, RADB | No ROA |
| 203.169.38.0/24 | NTTCOM, RADB | No ROA |
| 203.169.39.0/24 | NTTCOM, RADB | No ROA |
| 203.169.40.0/21 | NTTCOM, RADB | No ROA |
| 203.169.40.0/22 | NTTCOM, RADB | No ROA |
| 203.169.40.0/23 | NTTCOM, RADB | No ROA |
| 203.169.40.0/24 | NTTCOM, RADB | No ROA |
| 203.169.41.0/24 | NTTCOM, RADB | No ROA |
| 203.169.42.0/23 | NTTCOM, RADB | No ROA |
| 203.169.42.0/24 | NTTCOM, RADB | No ROA |
| 203.169.43.0/24 | NTTCOM, RADB | No ROA |
| 203.169.44.0/22 | NTTCOM, RADB | No ROA |
| 203.169.44.0/23 | NTTCOM, RADB | No ROA |
| 203.169.44.0/24 | NTTCOM, RADB | No ROA |
| 203.169.45.0/24 | NTTCOM, RADB | No ROA |
| 203.169.46.0/23 | NTTCOM, RADB | No ROA |
| 203.222.192.0/20 | NTTCOM, RADB | No ROA |
| 203.222.192.0/21 | NTTCOM, RADB | No ROA |
| 203.222.192.0/22 | NTTCOM, RADB | No ROA |
| 203.222.192.0/23 | NTTCOM, RADB | No ROA |
| 203.222.192.0/24 | NTTCOM, RADB | No ROA |
| 203.222.193.0/24 | NTTCOM, RADB | No ROA |
| 203.222.194.0/23 | NTTCOM, RADB | No ROA |
| 203.222.194.0/24 | NTTCOM, RADB | No ROA |
| 203.222.195.0/24 | NTTCOM, RADB | No ROA |
| 203.222.196.0/22 | NTTCOM, RADB | No ROA |
| 203.222.196.0/23 | NTTCOM, RADB | No ROA |
| 203.222.196.0/24 | NTTCOM, RADB | No ROA |
| 203.222.197.0/24 | NTTCOM, RADB | No ROA |
| 203.222.198.0/23 | NTTCOM, RADB | No ROA |
| 203.222.198.0/24 | NTTCOM, RADB | No ROA |
| 203.222.199.0/24 | NTTCOM, RADB | No ROA |
| 203.222.200.0/21 | NTTCOM, RADB | No ROA |
| 203.222.200.0/22 | NTTCOM, RADB | No ROA |
| 203.222.200.0/23 | NTTCOM, RADB | No ROA |
| 203.222.200.0/24 | NTTCOM, RADB | No ROA |
| 203.222.201.0/24 | NTTCOM, RADB | No ROA |
| 203.222.202.0/23 | NTTCOM, RADB | No ROA |
| 203.222.202.0/24 | NTTCOM, RADB | No ROA |
| 203.222.203.0/24 | NTTCOM, RADB | No ROA |
| 203.222.204.0/22 | NTTCOM, RADB | No ROA |
| 203.222.204.0/23 | NTTCOM, RADB | No ROA |
| 203.222.204.0/24 | NTTCOM, RADB | No ROA |
| 203.222.205.0/24 | NTTCOM, RADB | No ROA |
| 203.222.206.0/23 | NTTCOM, RADB | No ROA |
| 203.222.206.0/24 | NTTCOM, RADB | No ROA |
| 203.222.207.0/24 | NTTCOM, RADB | No ROA |
| 221.120.176.0/20 | APNIC, NTTCOM, RADB | No ROA |
| 221.120.176.0/21 | NTTCOM, RADB | No ROA |
| 221.120.176.0/22 | NTTCOM, RADB | No ROA |
| 221.120.176.0/23 | NTTCOM, RADB | No ROA |
| 221.120.178.0/23 | NTTCOM, RADB | No ROA |
| 221.120.178.0/24 | NTTCOM, RADB | No ROA |
| 221.120.180.0/22 | NTTCOM, RADB | No ROA |
| 221.120.180.0/23 | NTTCOM, RADB | No ROA |
| 221.120.181.0/24 | NTTCOM, RADB | No ROA |
| 221.120.182.0/23 | NTTCOM, RADB | No ROA |
| 221.120.182.0/24 | NTTCOM, RADB | No ROA |
| 221.120.184.0/21 | NTTCOM, RADB | No ROA |
| 221.120.184.0/22 | NTTCOM, RADB | No ROA |
| 221.120.184.0/23 | NTTCOM, RADB | No ROA |
| 221.120.186.0/23 | NTTCOM, RADB | No ROA |
| 221.120.188.0/22 | NTTCOM, RADB | No ROA |
| 221.120.188.0/23 | NTTCOM, RADB | No ROA |
| 221.120.188.0/24 | NTTCOM, RADB | No ROA |
| 221.120.190.0/23 | NTTCOM, RADB | No ROA |
| 221.120.190.0/24 | NTTCOM, RADB | No ROA |
| 221.120.191.0/24 | NTTCOM, 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.