Network · data from 2026-11-12
AS9660 KANNET-AS-AP - Telecommunication and ISP company
Registry name: KANNET-AS-AP - Telecommunication and ISP company, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9660, 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.
| 203.77.128.0/20 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.77.128.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.77.144.0/20 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 203.77.128.0/19 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS9660 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 67 are in fix.csv.
- ROA: none4
- Route object: RIR4
- Route object: not announced59
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.77.128.0/20 | No ROA covers it. Add a ROA for AS9660, maxLength 20. |
| Route object: RIR | 203.77.128.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.77.128.0/24 | No ROA covers it. Add a ROA for AS9660, maxLength 24. |
| Route object: RIR | 203.77.128.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.77.144.0/20 | No ROA covers it. Add a ROA for AS9660, maxLength 20. |
| Route object: RIR | 203.77.144.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.77.128.0/19 | No ROA covers it. Add a ROA for AS9660, maxLength 19. |
| Route object: RIR | 203.77.128.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9660 whose prefix no peer sees AS9660 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.77.128.0/21 | NTTCOM, RADB | No ROA |
| 203.77.128.0/22 | NTTCOM, RADB | No ROA |
| 203.77.128.0/23 | NTTCOM, RADB | No ROA |
| 203.77.129.0/24 | NTTCOM, RADB | No ROA |
| 203.77.130.0/23 | NTTCOM, RADB | No ROA |
| 203.77.130.0/24 | NTTCOM, RADB | No ROA |
| 203.77.131.0/24 | NTTCOM, RADB | No ROA |
| 203.77.132.0/22 | NTTCOM, RADB | No ROA |
| 203.77.132.0/23 | NTTCOM, RADB | No ROA |
| 203.77.132.0/24 | NTTCOM, RADB | No ROA |
| 203.77.133.0/24 | NTTCOM, RADB | No ROA |
| 203.77.134.0/23 | NTTCOM, RADB | No ROA |
| 203.77.134.0/24 | NTTCOM, RADB | No ROA |
| 203.77.135.0/24 | NTTCOM, RADB | No ROA |
| 203.77.136.0/21 | NTTCOM, RADB | No ROA |
| 203.77.136.0/22 | NTTCOM, RADB | No ROA |
| 203.77.136.0/23 | NTTCOM, RADB | No ROA |
| 203.77.136.0/24 | NTTCOM, RADB | No ROA |
| 203.77.137.0/24 | NTTCOM, RADB | No ROA |
| 203.77.138.0/23 | NTTCOM, RADB | No ROA |
| 203.77.138.0/24 | NTTCOM, RADB | No ROA |
| 203.77.139.0/24 | NTTCOM, RADB | No ROA |
| 203.77.140.0/22 | NTTCOM, RADB | No ROA |
| 203.77.140.0/23 | NTTCOM, RADB | No ROA |
| 203.77.140.0/24 | NTTCOM, RADB | No ROA |
| 203.77.141.0/24 | NTTCOM, RADB | No ROA |
| 203.77.142.0/23 | NTTCOM, RADB | No ROA |
| 203.77.142.0/24 | NTTCOM, RADB | No ROA |
| 203.77.143.0/24 | NTTCOM, RADB | No ROA |
| 203.77.144.0/21 | NTTCOM, RADB | No ROA |
| 203.77.144.0/22 | NTTCOM, RADB | No ROA |
| 203.77.144.0/23 | NTTCOM, RADB | No ROA |
| 203.77.144.0/24 | NTTCOM, RADB | No ROA |
| 203.77.145.0/24 | NTTCOM, RADB | No ROA |
| 203.77.146.0/23 | NTTCOM, RADB | No ROA |
| 203.77.146.0/24 | NTTCOM, RADB | No ROA |
| 203.77.147.0/24 | NTTCOM, RADB | No ROA |
| 203.77.148.0/22 | NTTCOM, RADB | No ROA |
| 203.77.148.0/23 | NTTCOM, RADB | No ROA |
| 203.77.148.0/24 | NTTCOM, RADB | No ROA |
| 203.77.149.0/24 | NTTCOM, RADB | No ROA |
| 203.77.150.0/23 | NTTCOM, RADB | No ROA |
| 203.77.150.0/24 | NTTCOM, RADB | No ROA |
| 203.77.151.0/24 | NTTCOM, RADB | No ROA |
| 203.77.152.0/21 | NTTCOM, RADB | No ROA |
| 203.77.152.0/22 | NTTCOM, RADB | No ROA |
| 203.77.152.0/23 | NTTCOM, RADB | No ROA |
| 203.77.152.0/24 | NTTCOM, RADB | No ROA |
| 203.77.153.0/24 | NTTCOM, RADB | No ROA |
| 203.77.154.0/23 | NTTCOM, RADB | No ROA |
| 203.77.154.0/24 | NTTCOM, RADB | No ROA |
| 203.77.155.0/24 | NTTCOM, RADB | No ROA |
| 203.77.156.0/22 | NTTCOM, RADB | No ROA |
| 203.77.156.0/23 | NTTCOM, RADB | No ROA |
| 203.77.156.0/24 | NTTCOM, RADB | No ROA |
| 203.77.157.0/24 | NTTCOM, RADB | No ROA |
| 203.77.158.0/23 | NTTCOM, RADB | No ROA |
| 203.77.158.0/24 | NTTCOM, RADB | No ROA |
| 203.77.159.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.