Network · data from 2026-11-12
AS38166 SCB1-AS-HK-AP - Standard Chartered Bank (Hong Kong) Limited.Banking and
Registry name: SCB1-AS-HK-AP - Standard Chartered Bank (Hong Kong) Limited.Banking and, HK · not in PeeringDB
61IPv4 routes
91.8% RPKI valid · 98.4% with a route object
0IPv6 routes
1RPKI invalid
1 origin · 0 maxLength
4No ROA
1 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
29Route objects not announced
registered with origin AS38166, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS38166, 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.
| 166.81.108.0/24 | Invalid: origin | None | 11 2%low visibility |
| 206.42.118.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.42.119.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 206.42.120.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 206.42.121.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 166.81.10.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.11.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.12.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.16.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.17.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.18.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.19.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.20.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.21.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.22.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.29.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.30.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.33.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.34.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.38.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.39.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.40.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.58.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.59.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.66.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.69.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.70.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.77.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.78.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.79.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.80.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.85.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.87.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.88.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.89.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.90.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.91.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.97.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.98.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.99.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.100.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.111.14.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.111.15.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 166.81.9.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 166.81.27.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 166.81.28.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.111.12.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 175.111.13.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 166.81.26.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.51.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.52.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.53.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.54.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.55.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.56.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.61.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.62.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.81.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.84.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 166.81.31.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 166.81.57.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS38166 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 39 are in fix.csv.
- ROA: origin1
- ROA: none4
- Route object: none1
- Route object: RIR4
- Route object: not announced29
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 166.81.108.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS38166 should announce it, add a ROA for AS38166. |
| Route object: none | 166.81.108.0/24 | No route object for it. Add a route object with origin AS38166 in the RIR database for the space. |
| ROA: none | 206.42.118.0/24 | No ROA covers it. Add a ROA for AS38166, maxLength 24. |
| Route object: RIR | 206.42.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.42.119.0/24 | No ROA covers it. Add a ROA for AS38166, maxLength 24. |
| Route object: RIR | 206.42.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.42.120.0/24 | No ROA covers it. Add a ROA for AS38166, maxLength 24. |
| Route object: RIR | 206.42.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 206.42.121.0/24 | No ROA covers it. Add a ROA for AS38166, maxLength 24. |
| Route object: RIR | 206.42.121.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38166 whose prefix no peer sees AS38166 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.75.175.0/24 | APNIC | Valid |
| 166.81.5.0/24 | APNIC | Valid |
| 166.81.13.0/24 | APNIC | Valid |
| 166.81.14.0/24 | APNIC | Valid |
| 166.81.15.0/24 | APNIC | Valid |
| 166.81.23.0/24 | APNIC | Valid |
| 166.81.24.0/24 | APNIC | Valid |
| 166.81.25.0/24 | APNIC | Valid |
| 166.81.35.0/24 | APNIC | Valid |
| 166.81.60.0/24 | APNIC | Valid |
| 166.81.65.0/24 | APNIC | Valid |
| 166.81.67.0/24 | APNIC | Valid |
| 166.81.68.0/24 | APNIC | Valid |
| 166.81.71.0/24 | APNIC | Invalid: origin |
| 166.81.83.0/24 | APNIC | Valid |
| 166.81.95.0/24 | APNIC | Valid |
| 166.81.96.0/24 | APNIC | Valid |
| 166.81.101.0/24 | APNIC | Valid |
| 166.81.102.0/24 | APNIC | Valid |
| 166.81.103.0/24 | APNIC | Valid |
| 166.81.104.0/24 | APNIC | Valid |
| 166.81.105.0/24 | APNIC | Valid |
| 166.81.106.0/24 | APNIC | Valid |
| 166.81.246.0/24 | APNIC | Valid |
| 166.81.247.0/24 | APNIC | Valid |
| 166.81.248.0/24 | APNIC | Valid |
| 166.81.249.0/24 | APNIC | Valid |
| 166.81.250.0/24 | APNIC | Valid |
| 203.191.3.0/24 | APNIC, RADB | 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.