Network · data from 2026-11-12
AS38277 CLINK-AS-AP - CommuniLink Internet Limited.
Registry name: CLINK-AS-AP - CommuniLink Internet Limited., HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38277, 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.124.8.0/22 | No ROA | Nonecovered by 203.124.8.0/21 | 152 23% |
| 43.252.40.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 43.252.41.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 43.252.42.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 43.252.165.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 43.252.166.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.124.9.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 203.124.11.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 43.252.164.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 43.252.167.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 203.124.10.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
AS-SET
AS38277 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 33 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced31
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.124.8.0/22 | No ROA covers it. Add a ROA for AS38277, maxLength 22. |
| Route object: none | 203.124.8.0/22 | No route object for it. A route object for 203.124.8.0/21 with origin AS38277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38277 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38277 whose prefix no peer sees AS38277 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.252.40.0/22 | NTTCOM, RADB | No ROA |
| 43.252.43.0/24 | NTTCOM, RADB | No ROA |
| 43.252.164.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.28.44.0/22 | APNIC, NTTCOM, RADB | Valid |
| 103.28.44.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.28.45.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.28.46.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.28.47.0/24 | APNIC, NTTCOM, RADB | Valid |
| 103.151.160.0/23 | NTTCOM, RADB | No ROA |
| 103.151.160.0/24 | NTTCOM, RADB | No ROA |
| 103.151.161.0/24 | NTTCOM, RADB | No ROA |
| 103.228.28.0/22 | RADB | No ROA |
| 103.228.28.0/24 | RADB | No ROA |
| 103.228.29.0/24 | RADB | No ROA |
| 103.228.30.0/24 | RADB | No ROA |
| 103.228.31.0/24 | NTTCOM, RADB | No ROA |
| 103.251.236.0/22 | NTTCOM, RADB | No ROA |
| 103.251.236.0/23 | NTTCOM, RADB | No ROA |
| 103.251.238.0/23 | NTTCOM, RADB | No ROA |
| 139.28.128.0/22 | NTTCOM, RADB | No ROA |
| 139.28.128.0/23 | NTTCOM, RADB | No ROA |
| 139.28.128.0/24 | NTTCOM, RADB | No ROA |
| 139.28.129.0/24 | NTTCOM, RADB | No ROA |
| 139.28.130.0/23 | NTTCOM, RADB | No ROA |
| 139.28.130.0/24 | NTTCOM, RADB | No ROA |
| 139.28.131.0/24 | NTTCOM, RADB | No ROA |
| 203.124.8.0/21 | NTTCOM, RADB | No ROA |
| 203.124.8.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.124.12.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.124.13.0/24 | APNIC, NTTCOM, RADB | Valid |
| 203.124.15.0/24 | APNIC, NTTCOM, 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.