bgpreport

Network · data from 2026-11-12

AS136198 ChinaNet-Guangdong-Yuexi-MAN - CHINANET Guangdong province Yuexi MAN network

Registry name: ChinaNet-Guangdong-Yuexi-MAN - CHINANET Guangdong province Yuexi MAN network, CN · not in PeeringDB

6IPv4 routes 50.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
79Route objects not announced registered with origin AS136198, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136198, 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.

146.222.79.0/24 No ROA Other IRR onlyRADB 672 100% 67
146.222.81.0/24 No ROA Other IRR onlyRADB 672 100% 67
146.222.94.0/24 No ROA Other IRR onlyRADB 672 100% 67
116.19.103.0/24 Valid Other IRR onlyRADB 672 100% 67
219.128.80.0/24 Valid Other IRR onlyRADB 672 100% 67
240e:108:4044::/48 Valid Other IRR onlyRADB 636 100% 68
240e:108:4844::/48 Valid Other IRR onlyRADB 636 100% 68
240e:3b0:222f::/48 Valid Other IRR onlyRADB 634 100% 67
240e:3b3:22f0::/44 Valid Other IRR onlyRADB 634 100% 67
240e:6b4:130::/44 Valid Other IRR onlyRADB 634 100% 67
14.21.102.0/24 Valid Other IRR onlyRADB 3 0%low visibility 4

AS-SET

AS136198 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 93 are in fix.csv.

  • ROA: none3
  • Route object: RIR11
  • Route object: not announced79
ChangePrefix or setDetailFull-table peers
ROA: none146.222.79.0/24No ROA covers it. Add a ROA for AS136198, maxLength 24.672 of 673
Route object: RIR146.222.79.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none146.222.81.0/24No ROA covers it. Add a ROA for AS136198, maxLength 24.672 of 673
Route object: RIR146.222.81.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none146.222.94.0/24No ROA covers it. Add a ROA for AS136198, maxLength 24.672 of 673
Route object: RIR146.222.94.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR116.19.103.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR219.128.80.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR240e:108:4044::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:108:4844::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:3b0:222f::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR240e:3b3:22f0::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR240e:6b4:130::/44Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR14.21.102.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

Route objects with origin AS136198 whose prefix no peer sees AS136198 announce. Many are kept on purpose (backup routes, space announced only in some places).

14.20.128.0/17RADBNo ROA
14.21.32.0/22RADBNo ROA
14.21.56.0/22RADBNo ROA
14.21.76.0/22RADBNo ROA
14.29.64.0/21RADBNo ROA
14.116.0.0/17RADBNo ROA
14.119.120.0/22RADBNo ROA
14.119.124.0/22RADBNo ROA
14.121.8.0/24RADBNo ROA
14.123.192.0/18RADBNo ROA
14.125.32.0/19RADBNo ROA
14.148.16.0/20RADBNo ROA
61.143.32.0/22RADBNo ROA
61.143.36.0/23RADBNo ROA
61.143.39.0/24RADBNo ROA
61.143.40.0/21RADBNo ROA
61.143.48.0/20RADBNo ROA
113.64.64.0/20RADBNo ROA
113.74.0.0/17RADBNo ROA
113.76.0.0/16RADBNo ROA
116.7.160.0/19RADBNo ROA
116.7.192.0/19RADBNo ROA
116.19.18.0/23RADBNo ROA
116.19.64.0/18RADBNo ROA
116.19.135.0/24RADBNo ROA
116.31.32.0/19RADBNo ROA
119.121.250.0/23RADBNo ROA
119.121.252.0/22RADBNo ROA
119.132.0.0/17RADBNo ROA
119.132.128.0/20RADBNo ROA
119.146.103.0/24RADBNo ROA
119.146.104.0/22RADBNo ROA
119.146.108.0/22RADBNo ROA
119.146.176.0/21RADBNo ROA
119.146.188.0/22RADBNo ROA
119.146.240.0/20RADBNo ROA
125.88.18.0/23RADBNo ROA
125.88.36.0/23RADBNo ROA
125.89.0.0/18RADBNo ROA
125.89.64.0/22RADBNo ROA
125.89.68.0/23RADBNo ROA
183.31.192.0/18RADBNo ROA
183.33.128.0/17RADBNo ROA
183.45.0.0/18RADBNo ROA
183.45.64.0/19RADBNo ROA
183.47.12.0/22RADBNo ROA
183.47.64.0/19RADBNo ROA
183.48.240.0/20RADBNo ROA
183.53.128.0/18RADBNo ROA
183.57.16.0/21RADBNo ROA
183.57.179.0/24RADBNo ROA
183.58.14.0/23RADBNo ROA
183.58.16.0/24RADBNo ROA
183.58.17.0/24RADBNo ROA
183.58.32.0/23RADBNo ROA
183.58.36.0/22RADBNo ROA
183.58.228.0/22RADBNo ROA
183.58.240.0/20RADBNo ROA
183.59.79.0/24RADBNo ROA
183.59.240.0/22RADBNo ROA
183.63.8.0/22RADBNo ROA
183.63.12.0/22RADBNo ROA
202.104.184.0/23RADBNo ROA
202.104.189.0/24RADBNo ROA
202.104.190.0/23RADBNo ROA
202.105.177.0/24RADBNo ROA
202.105.180.0/23RADBNo ROA
211.156.112.0/21RADBNo ROA
211.156.120.0/21RADBNo ROA
211.156.240.0/21RADBNo ROA
211.156.248.0/21RADBNo ROA
218.13.176.0/20RADBNo ROA
218.13.192.0/18RADBNo ROA
240e:1e:a000::/36RADBNo ROA
240e:fe:a000::/36RADBNo ROA
240e:fe:b000::/36RADBNo ROA
240e:ff:c007::/48RADBNo ROA
240e:ff:c00e::/48RADBNo ROA
240e:7b6:4000::/36RADBNo 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.