Network · data from 2026-11-12
AS24462 HKJC-AS-HK-AP - Network Management Section
Registry name: HKJC-AS-HK-AP - Network Management Section, HK · not in PeeringDB
32IPv4 routes
65.6% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
11No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
17Route objects not announced
registered with origin AS24462, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS24462, 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.82.8.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.82.9.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.10.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.10.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.11.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.12.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.12.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.13.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.14.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 203.82.15.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.82.8.0/21 | No ROA | Other IRR onlyRADB | 176 26% |
| 101.78.204.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 101.78.205.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 101.78.206.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 101.78.207.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 116.92.130.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 203.174.32.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 220.232.228.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 220.232.229.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 101.78.204.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 174 26% |
| 58.64.251.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 59.148.165.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.143.60.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.143.119.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 118.143.137.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.143.138.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.143.142.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.143.159.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 210.0.224.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 218.188.80.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 218.189.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 118.143.160.0/24 | Valid | RIR databaseAPNIC, RADB | 658 98% |
AS-SET
AS24462 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 48 are in fix.csv.
- ROA: none11
- Route object: RIR20
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.82.8.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.8.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.9.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.10.0/23 | No ROA covers it. Add a ROA for AS24462, maxLength 23. |
| Route object: RIR | 203.82.10.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.10.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.11.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.12.0/23 | No ROA covers it. Add a ROA for AS24462, maxLength 23. |
| Route object: RIR | 203.82.12.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.12.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.13.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.14.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.15.0/24 | No ROA covers it. Add a ROA for AS24462, maxLength 24. |
| Route object: RIR | 203.82.15.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.82.8.0/21 | No ROA covers it. Add a ROA for AS24462, maxLength 21. |
| Route object: RIR | 203.82.8.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 101.78.204.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 101.78.205.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 101.78.206.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 101.78.207.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 116.92.130.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 203.174.32.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 220.232.228.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 220.232.229.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 101.78.204.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24462 whose prefix no peer sees AS24462 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 101.78.204.0/23 | NTTCOM | Valid |
| 101.78.206.0/23 | NTTCOM | Valid |
| 118.143.96.96/32 | APNIC | Valid |
| 118.143.96.97/32 | APNIC | Valid |
| 118.143.96.98/32 | APNIC | Valid |
| 118.143.96.99/32 | APNIC | Valid |
| 118.143.96.108/32 | APNIC | Valid |
| 118.143.96.109/32 | APNIC | Valid |
| 118.143.96.110/32 | APNIC | Valid |
| 118.143.96.111/32 | APNIC | Valid |
| 118.143.96.152/32 | APNIC | Valid |
| 118.143.96.153/32 | APNIC | Valid |
| 118.143.96.154/32 | APNIC | Valid |
| 118.143.170.0/24 | APNIC, RADB | Valid |
| 202.77.51.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.82.12.0/22 | RADB | No ROA |
| 203.82.14.0/23 | 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.