Network · data from 2026-11-12
AS45348 Chuan Wei (Cambodia) Co., Ltd.
Registry name: CHUANWEI-AS-KH - Regency Square, Complex B,, KH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS45348, 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.
| 111.67.105.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 5 1%low visibility |
| 111.67.106.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 5 1%low visibility |
| 111.67.108.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 5 1%low visibility |
AS-SET
AS45348'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 29 are in fix.csv.
- ROA: none3
- Route object: RIR3
- Route object: not announced23
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 111.67.105.0/24 | No ROA covers it. Add a ROA for AS45348, maxLength 24. |
| Route object: RIR | 111.67.105.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.67.106.0/24 | No ROA covers it. Add a ROA for AS45348, maxLength 24. |
| Route object: RIR | 111.67.106.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 111.67.108.0/24 | No ROA covers it. Add a ROA for AS45348, maxLength 24. |
| Route object: RIR | 111.67.108.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS45348 whose prefix no peer sees AS45348 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.246.228.0/22 | NTTCOM, RADB | No ROA |
| 103.246.228.0/23 | NTTCOM, RADB | No ROA |
| 103.246.228.0/24 | NTTCOM | No ROA |
| 103.246.229.0/24 | NTTCOM, RADB | No ROA |
| 103.246.230.0/23 | NTTCOM, RADB | No ROA |
| 103.246.230.0/24 | NTTCOM, RADB | No ROA |
| 103.246.231.0/24 | NTTCOM, RADB | No ROA |
| 111.67.96.0/20 | NTTCOM, RADB | No ROA |
| 111.67.96.0/21 | NTTCOM, RADB | No ROA |
| 111.67.104.0/21 | NTTCOM, RADB | No ROA |
| 111.67.104.0/22 | NTTCOM, RADB | No ROA |
| 111.67.104.0/23 | NTTCOM, RADB | No ROA |
| 111.67.104.0/24 | NTTCOM, RADB | No ROA |
| 111.67.106.0/23 | NTTCOM, RADB | No ROA |
| 111.67.107.0/24 | NTTCOM, RADB | No ROA |
| 111.67.108.0/22 | NTTCOM, RADB | No ROA |
| 111.67.108.0/23 | NTTCOM, RADB | No ROA |
| 111.67.109.0/24 | NTTCOM, RADB | No ROA |
| 111.67.110.0/23 | NTTCOM, RADB | No ROA |
| 111.67.110.0/24 | NTTCOM, RADB | No ROA |
| 111.67.111.0/24 | NTTCOM, RADB | No ROA |
| 124.108.4.0/22 | APNIC | Invalid: origin |
| 2407:5e00::/32 | 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.