Network · data from 2026-11-12
AS7540 IXTech
Registry name: HKCIX-AS-AP - HongKong Commercial Internet Exchange, HK · PeeringDB
99IPv4 routes
90.9% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
9No ROA
0 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
105Route objects not announced
registered with origin AS7540, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS7540, 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.
| 202.53.128.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 202.53.130.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 202.181.175.0/24 | No ROA | Other IRR onlyNTTCOM, REACH | 2 0%low visibility |
| 202.181.189.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
| 103.79.92.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.79.93.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.79.94.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.79.95.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.181.232.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 202.181.154.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.181.216.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 202.181.220.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.181.223.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 117.18.96.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.98.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.105.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.106.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.107.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.108.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.112.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.113.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.114.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.115.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.116.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.119.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.120.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.121.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 117.18.122.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 202.181.141.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.146.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 202.181.147.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.150.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 202.181.152.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 202.181.160.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.161.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.162.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.163.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.164.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.165.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.166.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.167.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.168.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.169.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.170.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.172.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.173.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.174.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.176.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.178.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.184.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 202.181.186.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 202.181.187.0/24 | Valid | RIR databaseAPNIC, NTTCOM, REACH | 671 100% |
| 202.181.192.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.193.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.194.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.195.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.196.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.197.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.198.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.199.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.200.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.201.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.202.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.203.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.205.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.206.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.207.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.208.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.209.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.210.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.211.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.212.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.213.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.214.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.215.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.218.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 202.181.224.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.225.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.226.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.227.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.228.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.230.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.231.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.233.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.234.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.235.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.236.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.237.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.238.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.239.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.240.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.241.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.242.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.243.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.244.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.245.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.246.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.247.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 202.181.217.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS7540's PeeringDB record names no 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 118 are in fix.csv.
- ROA: none9
- Route object: RIR4
- Route object: not announced105
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.53.128.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| Route object: RIR | 202.53.128.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.53.130.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| Route object: RIR | 202.53.130.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 202.181.175.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| Route object: RIR | 202.181.175.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| ROA: none | 202.181.189.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| Route object: RIR | 202.181.189.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.79.92.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| ROA: none | 103.79.93.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| ROA: none | 103.79.94.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| ROA: none | 103.79.95.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
| ROA: none | 202.181.232.0/24 | No ROA covers it. Add a ROA for AS7540, maxLength 24. |
Route objects not announced
Route objects with origin AS7540 whose prefix no peer sees AS7540 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 110.76.190.0/24 | NTTCOM, RADB | No ROA |
| 117.18.64.0/20 | REACH | No ROA |
| 117.18.64.0/24 | REACH | No ROA |
| 117.18.65.0/24 | REACH | No ROA |
| 117.18.66.0/24 | REACH | No ROA |
| 117.18.67.0/24 | REACH | Invalid: origin |
| 117.18.68.0/24 | REACH | No ROA |
| 117.18.69.0/24 | REACH | No ROA |
| 117.18.70.0/24 | REACH | No ROA |
| 117.18.71.0/24 | REACH | No ROA |
| 117.18.72.0/24 | REACH | Invalid: origin |
| 117.18.73.0/24 | REACH | No ROA |
| 117.18.74.0/24 | REACH | Invalid: origin |
| 117.18.75.0/24 | REACH | No ROA |
| 117.18.76.0/24 | REACH | No ROA |
| 117.18.77.0/24 | REACH | No ROA |
| 117.18.78.0/24 | REACH | Invalid: origin |
| 117.18.79.0/24 | REACH | No ROA |
| 117.18.96.0/19 | REACH | No ROA |
| 117.18.97.0/24 | REACH | No ROA |
| 117.18.99.0/24 | REACH | Invalid: origin |
| 117.18.100.0/24 | REACH | Invalid: origin |
| 117.18.101.0/24 | REACH | Invalid: origin |
| 117.18.102.0/24 | REACH | Invalid: origin |
| 117.18.103.0/24 | REACH | Invalid: origin |
| 117.18.104.0/24 | REACH | Invalid: origin |
| 117.18.106.0/23 | APNIC | Valid |
| 117.18.108.0/23 | APNIC | Valid |
| 117.18.109.0/24 | APNIC, REACH | Valid |
| 117.18.110.0/24 | REACH | No ROA |
| 117.18.111.0/24 | REACH | No ROA |
| 117.18.112.0/22 | APNIC | Valid |
| 117.18.117.0/24 | REACH | Invalid: origin |
| 117.18.118.0/24 | NTTCOM, REACH | No ROA |
| 117.18.120.0/23 | APNIC | Valid |
| 117.18.123.0/24 | REACH | Invalid: origin |
| 117.18.124.0/24 | REACH | Invalid: origin |
| 117.18.125.0/24 | REACH | Invalid: origin |
| 117.18.126.0/24 | REACH | Invalid: origin |
| 117.18.127.0/24 | REACH | Invalid: origin |
| 117.121.47.0/24 | NTTCOM | No ROA |
| 123.242.224.0/21 | REACH | No ROA |
| 123.242.224.0/24 | REACH | No ROA |
| 123.242.225.0/24 | REACH | No ROA |
| 123.242.226.0/24 | REACH | No ROA |
| 123.242.227.0/24 | REACH | No ROA |
| 123.242.228.0/24 | REACH | No ROA |
| 123.242.229.0/24 | REACH | No ROA |
| 123.242.230.0/24 | REACH | No ROA |
| 123.242.231.0/24 | REACH | No ROA |
| 125.62.224.0/20 | REACH | Invalid: origin |
| 125.62.224.0/24 | REACH | Invalid: origin |
| 125.62.225.0/24 | REACH | Invalid: origin |
| 125.62.226.0/24 | REACH | Invalid: origin |
| 125.62.227.0/24 | REACH | Invalid: origin |
| 125.62.228.0/24 | REACH | Invalid: origin |
| 125.62.229.0/24 | REACH | Invalid: origin |
| 125.62.230.0/24 | REACH | Invalid: origin |
| 125.62.231.0/24 | REACH | Invalid: origin |
| 125.62.232.0/24 | REACH | Invalid: origin |
| 125.62.233.0/24 | REACH | Invalid: origin |
| 125.62.234.0/24 | REACH | Invalid: origin |
| 125.62.235.0/24 | REACH | Invalid: origin |
| 125.62.236.0/24 | REACH | Invalid: origin |
| 125.62.237.0/24 | REACH | Invalid: origin |
| 125.62.238.0/24 | REACH | Invalid: origin |
| 125.62.239.0/24 | REACH | Invalid: origin |
| 183.182.16.0/24 | REACH | No ROA |
| 202.0.182.0/23 | REACH | No ROA |
| 202.3.6.0/23 | REACH | No ROA |
| 202.52.128.0/22 | REACH | No ROA |
| 202.52.136.0/21 | REACH | No ROA |
| 202.52.144.0/20 | REACH | No ROA |
| 202.140.180.0/24 | REACH | Invalid: origin |
| 202.140.182.0/24 | REACH | Invalid: origin |
| 202.181.128.0/23 | REACH | Invalid: origin |
| 202.181.132.0/22 | REACH | Invalid: origin |
| 202.181.136.0/24 | APNIC | Valid |
| 202.181.140.0/24 | APNIC | Valid |
| 202.181.156.0/24 | NTTCOM, REACH | No ROA |
| 202.181.157.0/24 | NTTCOM, REACH | No ROA |
| 202.181.158.0/24 | NTTCOM, REACH | No ROA |
| 202.181.159.0/24 | NTTCOM, REACH | No ROA |
| 202.181.160.0/19 | REACH | No ROA |
| 202.181.160.0/20 | APNIC | No ROA |
| 202.181.184.0/22 | APNIC | Valid |
| 202.181.185.0/24 | REACH | Invalid: maxLength |
| 202.181.191.0/24 | NTTCOM, RADB | No ROA |
| 202.181.192.0/19 | REACH | No ROA |
| 202.181.192.0/21 | APNIC | Valid |
| 202.181.204.0/24 | REACH | Invalid: origin |
| 202.181.208.0/21 | APNIC | Valid |
| 202.181.224.0/20 | APNIC, REACH | No ROA |
| 202.181.232.0/23 | APNIC | No ROA |
| 202.181.240.0/21 | REACH | No ROA |
| 202.181.248.0/22 | RADB | No ROA |
| 202.181.248.0/23 | REACH | No ROA |
| 202.181.248.0/24 | NTTCOM | No ROA |
| 202.181.249.0/24 | NTTCOM, REACH | No ROA |
| 202.181.250.0/23 | REACH | No ROA |
| 202.181.252.0/23 | REACH | Invalid: origin |
| 203.90.227.0/24 | REACH | Invalid: origin |
| 203.90.228.0/24 | REACH | Invalid: origin |
| 2405:5d00::/32 | APNIC | Valid |
| 2405:5d00::/64 | APNIC | Valid |
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.