Network · data from 2026-11-12
AS24492 WiCAM Corporation, Ltd
Registry name: IIT-WICAM-AS-AP - WiCAM Corporation Ltd., KH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24492, 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.
| 2405:1a00::/48 | Invalid: maxLength | Nonecovered by 2405:1a00::/36 | 66 10% |
| 27.111.8.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 43.245.216.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 49.156.32.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 103.17.212.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 116.206.16.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 119.15.80.0/20 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 185.175.228.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.79.24.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 218.100.71.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 669 99% |
| 2405:1a00::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2405:1a00::/33 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:1000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:2000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:2000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:3000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:4000::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:4000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:4000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:5000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:6000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:6000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:7000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:8000::/33 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:8000::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:8000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:8000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:9000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:a000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:a000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:b000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:c000::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:c000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:c000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:d000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:e000::/35 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:e000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2405:1a00:f000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 27.111.8.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 27.111.10.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 43.245.216.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 43.245.216.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 43.245.217.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 43.245.218.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 43.245.218.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 43.245.219.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 49.156.32.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 49.156.32.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 49.156.32.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 49.156.36.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 49.156.36.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 474 70% |
| 103.17.212.0/23 | Valid | RIR databaseAPNIC, RADB | 474 70% |
| 27.111.8.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 27.111.9.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 27.111.10.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 27.111.11.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 116.206.16.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 116.206.16.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 116.206.17.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 116.206.18.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 116.206.18.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 116.206.19.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 473 70% |
| 103.17.214.0/23 | Valid | RIR databaseAPNIC, RADB | 472 70% |
| 119.15.80.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.80.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.80.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.82.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.84.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.84.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.86.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.88.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.88.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.88.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.90.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.92.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.92.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 119.15.94.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 469 70% |
| 185.175.228.0/23 | Valid | RIR databaseAPNIC, RADB | 469 70% |
| 185.175.228.0/24 | Valid | RIR databaseAPNIC, RADB | 469 70% |
| 185.175.229.0/24 | Valid | RIR databaseAPNIC, RADB | 469 70% |
| 185.175.230.0/23 | Valid | RIR databaseAPNIC, RADB | 469 70% |
| 185.175.230.0/24 | Valid | RIR databaseAPNIC, RADB | 469 70% |
| 185.175.231.0/24 | Valid | RIR databaseAPNIC, RADB | 469 70% |
| 202.79.24.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 468 70% |
| 202.79.24.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 468 70% |
| 202.79.26.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 468 70% |
| 202.79.28.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 468 70% |
| 202.79.30.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 468 70% |
| 103.17.213.0/24 | Valid | RIR databaseAPNIC, RADB | 213 32% |
| 103.17.214.0/24 | Valid | RIR databaseAPNIC, RADB | 213 32% |
| 103.17.215.0/24 | Valid | RIR databaseAPNIC, RADB | 213 32% |
| 49.156.32.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.33.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.34.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.35.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.36.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.37.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.38.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.39.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.40.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.41.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.42.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.43.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.44.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.45.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.46.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.47.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.80.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.81.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.82.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.83.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.84.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.85.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.87.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.91.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.92.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.93.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.94.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 119.15.95.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.24.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.25.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.26.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.27.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.28.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.29.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB, REACH | 196 29% |
| 202.79.30.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 202.79.31.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 196 29% |
| 49.156.34.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.38.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.40.0/21 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.40.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.40.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.42.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.44.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
| 49.156.44.0/23 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS24492: AS-WICAM-KH. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS24492 isn't in the set, or no route object for AS24492 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS24492 in it | Not covered |
|---|---|---|---|---|---|
| AS-WICAM-KH | APNIC | 6 | 1 | Yes | 0 |
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 49 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced47
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2405:1a00::/48 | ROA 2405:1a00::/32 AS24492 has maxLength 36; the route is a /48. Raise the maxLength, or add a ROA for 2405:1a00::/48. |
| Route object: none | 2405:1a00::/48 | No route object for it. A route object for 2405:1a00::/36 with origin AS24492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24492 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24492 whose prefix no peer sees AS24492 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.150.104.0/22 | NTTCOM | No ROA |
| 38.150.104.0/23 | NTTCOM, RADB | No ROA |
| 38.150.104.0/24 | NTTCOM, RADB | No ROA |
| 38.150.105.0/24 | NTTCOM, RADB | No ROA |
| 38.150.106.0/23 | NTTCOM, RADB | No ROA |
| 38.150.106.0/24 | NTTCOM, RADB | No ROA |
| 38.150.107.0/24 | NTTCOM, RADB | No ROA |
| 49.156.46.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.17.212.0/24 | APNIC, RADB | Valid |
| 103.110.228.0/22 | RADB | No ROA |
| 103.121.188.0/22 | RADB | No ROA |
| 103.197.104.0/22 | RADB | No ROA |
| 103.197.104.0/23 | NTTCOM, RADB | No ROA |
| 117.55.254.0/23 | RADB | No ROA |
| 202.79.28.0/23 | APNIC, NTTCOM, RADB | Valid |
| 203.82.224.0/20 | RADB | No ROA |
| 203.82.224.0/21 | RADB | No ROA |
| 203.82.224.0/22 | RADB | No ROA |
| 203.82.224.0/23 | RADB | No ROA |
| 203.82.224.0/24 | RADB | No ROA |
| 203.82.225.0/24 | RADB | No ROA |
| 203.82.226.0/23 | RADB | No ROA |
| 203.82.226.0/24 | RADB | No ROA |
| 203.82.227.0/24 | RADB | No ROA |
| 203.82.228.0/22 | RADB | No ROA |
| 203.82.228.0/23 | RADB | No ROA |
| 203.82.228.0/24 | RADB | No ROA |
| 203.82.229.0/24 | RADB | No ROA |
| 203.82.230.0/23 | RADB | No ROA |
| 203.82.230.0/24 | RADB | No ROA |
| 203.82.231.0/24 | RADB | No ROA |
| 203.82.232.0/21 | RADB | No ROA |
| 203.82.232.0/22 | RADB | No ROA |
| 203.82.232.0/23 | RADB | No ROA |
| 203.82.232.0/24 | RADB | No ROA |
| 203.82.233.0/24 | RADB | No ROA |
| 203.82.234.0/23 | RADB | No ROA |
| 203.82.234.0/24 | RADB | No ROA |
| 203.82.235.0/24 | RADB | No ROA |
| 203.82.236.0/22 | RADB | No ROA |
| 203.82.236.0/23 | RADB | No ROA |
| 203.82.236.0/24 | RADB | No ROA |
| 203.82.237.0/24 | RADB | No ROA |
| 203.82.238.0/23 | RADB | No ROA |
| 203.82.238.0/24 | RADB | No ROA |
| 203.82.239.0/24 | RADB | No ROA |
| 220.158.148.0/22 | 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.