bgpreport

Network · data from 2026-11-12

AS9389 CGWNET - BEIJING SHENZHOU GREATWALL COMMUNICATION

Registry name: CGWNET - BEIJING SHENZHOU GREATWALL COMMUNICATION, CN · not in PeeringDB

35IPv4 routes 85.7% RPKI valid · 0.0% with a route object
1IPv6 routes 100.0% RPKI valid · 0.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
4No ROA 36 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS9389, seen from no peer

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% 48
103.155.76.0/24 No ROA None 673 100% 67
103.155.77.0/24 No ROA None 673 100% 67
210.79.224.0/20 No ROA None 672 100% 67
210.79.240.0/20 No ROA None 672 100% 67
103.235.144.0/24 Valid None 673 100% 67
113.49.16.0/20 Valid None 673 100% 67
113.50.0.0/20 Valid None 673 100% 67
113.50.32.0/24 Valid None 673 100% 67
113.50.48.0/20 Valid None 673 100% 67
113.50.64.0/24 Valid None 673 100% 67
113.50.65.0/24 Valid None 673 100% 67
113.50.66.0/24 Valid None 673 100% 67
113.50.67.0/24 Valid None 673 100% 67
113.50.68.0/22 Valid None 673 100% 67
113.50.72.0/21 Valid None 673 100% 67
118.64.0.0/22 Valid None 673 100% 67
118.64.4.0/22 Valid None 673 100% 67
118.64.248.0/22 Valid None 673 100% 67
118.64.252.0/22 Valid None 673 100% 67
118.65.0.0/21 Valid None 673 100% 67
118.66.184.0/24 Valid None 673 100% 67
121.39.255.0/24 Valid None 673 100% 67
211.165.0.0/16 Valid None 673 100% 67
211.166.0.0/16 Valid None 673 100% 67
211.166.4.0/22 Valid None 673 100% 67
211.166.8.0/21 Valid None 673 100% 67
211.166.17.0/24 Valid None 673 100% 67
211.166.246.0/24 Valid None 673 100% 67
211.166.247.0/24 Valid None 673 100% 67
211.166.249.0/24 Valid None 673 100% 67
211.166.250.0/24 Valid None 673 100% 67
113.48.48.0/20 Valid None 543 81% 67
113.48.224.0/20 Valid None 543 81% 67
118.66.224.0/20 Valid None 543 81% 67
2001:4510:400::/40 Valid None 399 63% 67

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
ChangePrefix or setDetailFull-table peers
ROA: maxLength211.166.253.0/24ROA 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.104 of 673
Route object: none211.166.253.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.104 of 673
ROA: none103.155.76.0/24No ROA covers it. Add a ROA for AS9389, maxLength 24.673 of 673
Route object: none103.155.76.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
ROA: none103.155.77.0/24No ROA covers it. Add a ROA for AS9389, maxLength 24.673 of 673
Route object: none103.155.77.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
ROA: none210.79.224.0/20No ROA covers it. Add a ROA for AS9389, maxLength 20.672 of 673
Route object: none210.79.224.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.672 of 673
ROA: none210.79.240.0/20No ROA covers it. Add a ROA for AS9389, maxLength 20.672 of 673
Route object: none210.79.240.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.672 of 673
Route object: none103.235.144.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.49.16.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.0.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.32.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.48.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.64.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.65.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.66.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.67.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.68.0/22No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.50.72.0/21No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none118.64.0.0/22No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none118.64.4.0/22No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none118.64.248.0/22No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none118.64.252.0/22No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none118.65.0.0/21No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none118.66.184.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none121.39.255.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.165.0.0/16No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.0.0/16No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.4.0/22No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.8.0/21No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.17.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.246.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.247.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.249.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none211.166.250.0/24No route object for it. Add a route object with origin AS9389 in the RIR database for the space.673 of 673
Route object: none113.48.48.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.543 of 673
Route object: none113.48.224.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.543 of 673
Route object: none118.66.224.0/20No route object for it. Add a route object with origin AS9389 in the RIR database for the space.543 of 673
Route object: none2001:4510:400::/40No route object for it. Add a route object with origin AS9389 in the RIR database for the space.399 of 636

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.