Network · data from 2026-11-12
AS9389 CGWNET - BEIJING SHENZHOU GREATWALL COMMUNICATION
Registry name: CGWNET - BEIJING SHENZHOU GREATWALL COMMUNICATION, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9389, 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.
| 211.166.253.0/24 | Invalid: maxLength | None | 104 15% |
| 103.155.76.0/24 | No ROA | None | 673 100% |
| 103.155.77.0/24 | No ROA | None | 673 100% |
| 210.79.224.0/20 | No ROA | None | 672 100% |
| 210.79.240.0/20 | No ROA | None | 672 100% |
| 103.235.144.0/24 | Valid | None | 673 100% |
| 113.49.16.0/20 | Valid | None | 673 100% |
| 113.50.0.0/20 | Valid | None | 673 100% |
| 113.50.32.0/24 | Valid | None | 673 100% |
| 113.50.48.0/20 | Valid | None | 673 100% |
| 113.50.64.0/24 | Valid | None | 673 100% |
| 113.50.65.0/24 | Valid | None | 673 100% |
| 113.50.66.0/24 | Valid | None | 673 100% |
| 113.50.67.0/24 | Valid | None | 673 100% |
| 113.50.68.0/22 | Valid | None | 673 100% |
| 113.50.72.0/21 | Valid | None | 673 100% |
| 118.64.0.0/22 | Valid | None | 673 100% |
| 118.64.4.0/22 | Valid | None | 673 100% |
| 118.64.248.0/22 | Valid | None | 673 100% |
| 118.64.252.0/22 | Valid | None | 673 100% |
| 118.65.0.0/21 | Valid | None | 673 100% |
| 118.66.184.0/24 | Valid | None | 673 100% |
| 121.39.255.0/24 | Valid | None | 673 100% |
| 211.165.0.0/16 | Valid | None | 673 100% |
| 211.166.0.0/16 | Valid | None | 673 100% |
| 211.166.4.0/22 | Valid | None | 673 100% |
| 211.166.8.0/21 | Valid | None | 673 100% |
| 211.166.17.0/24 | Valid | None | 673 100% |
| 211.166.246.0/24 | Valid | None | 673 100% |
| 211.166.247.0/24 | Valid | None | 673 100% |
| 211.166.249.0/24 | Valid | None | 673 100% |
| 211.166.250.0/24 | Valid | None | 673 100% |
| 113.48.48.0/20 | Valid | None | 543 81% |
| 113.48.224.0/20 | Valid | None | 543 81% |
| 118.66.224.0/20 | Valid | None | 543 81% |
| 2001:4510:400::/40 | Valid | None | 399 63% |
AS-SET
AS9389 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 41 are in fix.csv.
- ROA: maxLength1
- ROA: none4
- Route object: none36
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 211.166.253.0/24 | ROA 211.166.0.0/16 AS9389 has maxLength 16; the route is a /24. Raise the maxLength, or add a ROA for 211.166.253.0/24. |
| Route object: none | 211.166.253.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| ROA: none | 103.155.76.0/24 | No ROA covers it. Add a ROA for AS9389, maxLength 24. |
| Route object: none | 103.155.76.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| ROA: none | 103.155.77.0/24 | No ROA covers it. Add a ROA for AS9389, maxLength 24. |
| Route object: none | 103.155.77.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| ROA: none | 210.79.224.0/20 | No ROA covers it. Add a ROA for AS9389, maxLength 20. |
| Route object: none | 210.79.224.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| ROA: none | 210.79.240.0/20 | No ROA covers it. Add a ROA for AS9389, maxLength 20. |
| Route object: none | 210.79.240.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 103.235.144.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.49.16.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.0.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.32.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.48.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.64.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.65.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.66.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.67.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.68.0/22 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.50.72.0/21 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.64.0.0/22 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.64.4.0/22 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.64.248.0/22 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.64.252.0/22 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.65.0.0/21 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.66.184.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 121.39.255.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.165.0.0/16 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.0.0/16 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.4.0/22 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.8.0/21 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.17.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.246.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.247.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.249.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 211.166.250.0/24 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.48.48.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 113.48.224.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 118.66.224.0/20 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
| Route object: none | 2001:4510:400::/40 | No route object for it. Add a route object with origin AS9389 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS9389 is announced.
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.