Network · data from 2026-11-12
AS17988 CSC-HK-AS-AP - China Satellite Communications (HongKong) Corporation Limited
Registry name: CSC-HK-AS-AP - China Satellite Communications (HongKong) Corporation Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17988, 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.222.192.0/22 | No ROA | Other origin onlycovered by 203.222.192.0/20 | 670 100% |
| 203.222.196.0/22 | No ROA | Other origin onlycovered by 203.222.192.0/20 | 670 100% |
| 203.222.192.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.193.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.194.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.196.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.197.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.198.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.199.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 670 100% |
| 203.222.195.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 2 0%low visibility |
| 203.222.192.0/20 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
AS-SET
AS17988 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 64 are in fix.csv.
- ROA: none11
- Route object: none2
- Route object: RIR8
- Route object: not announced43
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.222.192.0/22 | No ROA covers it. Add a ROA for AS17988, maxLength 22. |
| Route object: none | 203.222.192.0/22 | Route objects for it name AS17975. A route object for 203.222.192.0/20 with origin AS17988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17988 in the RIR database for the space. |
| ROA: none | 203.222.196.0/22 | No ROA covers it. Add a ROA for AS17988, maxLength 22. |
| Route object: none | 203.222.196.0/22 | Route objects for it name AS17975. A route object for 203.222.192.0/20 with origin AS17988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17988 in the RIR database for the space. |
| ROA: none | 203.222.192.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.192.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.193.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.193.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.194.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.194.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.196.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.196.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.197.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.197.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.198.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.198.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.199.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.199.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.195.0/24 | No ROA covers it. Add a ROA for AS17988, maxLength 24. |
| Route object: RIR | 203.222.195.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 203.222.192.0/20 | No ROA covers it. Add a ROA for AS17988, maxLength 20. |
Route objects not announced
Route objects with origin AS17988 whose prefix no peer sees AS17988 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.176.224.0/19 | NTTCOM | No ROA |
| 202.176.224.0/24 | NTTCOM | No ROA |
| 202.176.225.0/24 | NTTCOM | No ROA |
| 202.176.226.0/24 | NTTCOM | No ROA |
| 202.176.227.0/24 | NTTCOM | No ROA |
| 202.176.228.0/24 | NTTCOM | No ROA |
| 202.176.229.0/24 | NTTCOM | No ROA |
| 202.176.230.0/24 | NTTCOM | No ROA |
| 202.176.231.0/24 | NTTCOM | No ROA |
| 202.176.232.0/24 | NTTCOM | No ROA |
| 202.176.233.0/24 | NTTCOM | No ROA |
| 202.176.234.0/24 | NTTCOM | No ROA |
| 202.176.235.0/24 | NTTCOM | No ROA |
| 202.176.236.0/24 | NTTCOM | No ROA |
| 202.176.237.0/24 | NTTCOM | No ROA |
| 202.176.238.0/24 | NTTCOM | No ROA |
| 202.176.239.0/24 | NTTCOM | No ROA |
| 202.176.240.0/24 | NTTCOM | No ROA |
| 202.176.241.0/24 | NTTCOM | No ROA |
| 202.176.242.0/24 | NTTCOM | No ROA |
| 202.176.243.0/24 | NTTCOM | No ROA |
| 202.176.244.0/24 | NTTCOM | No ROA |
| 202.176.245.0/24 | NTTCOM | No ROA |
| 202.176.246.0/24 | NTTCOM | No ROA |
| 202.176.247.0/24 | NTTCOM | No ROA |
| 202.176.248.0/24 | NTTCOM | No ROA |
| 202.176.249.0/24 | NTTCOM | No ROA |
| 202.176.250.0/24 | NTTCOM | No ROA |
| 202.176.251.0/24 | NTTCOM | No ROA |
| 202.176.252.0/24 | NTTCOM | No ROA |
| 202.176.253.0/24 | NTTCOM | No ROA |
| 202.176.254.0/24 | NTTCOM | No ROA |
| 202.176.255.0/24 | NTTCOM | No ROA |
| 203.222.200.0/24 | NTTCOM, RADB | No ROA |
| 203.222.201.0/24 | NTTCOM, RADB | No ROA |
| 203.222.202.0/24 | NTTCOM, RADB | No ROA |
| 203.222.203.0/24 | NTTCOM, RADB | No ROA |
| 203.222.204.0/24 | NTTCOM, RADB | No ROA |
| 203.222.205.0/24 | NTTCOM, RADB | No ROA |
| 203.222.206.0/24 | NTTCOM, RADB | No ROA |
| 203.222.207.0/24 | NTTCOM, RADB | No ROA |
| 221.120.190.0/24 | NTTCOM, RADB | No ROA |
| 2407:7280::/32 | APNIC | 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.