bgpreport

Network · data from 2026-11-12

AS140486 CHINATELECOM-ZHEJIANG-JINHUA-5GC-NETWORK - CHINATELECOM ZHEJIANG province JINHUA 5GC network

Registry name: CHINATELECOM-ZHEJIANG-JINHUA-5GC-NETWORK - CHINATELECOM ZHEJIANG province JINHUA 5GC network, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140486, 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.
60.163.66.0/23 Valid Other IRR onlyRADB 672 100% 67
115.220.65.0/24 Valid Other IRR onlyRADB 672 100% 67
115.233.186.0/24 Valid Other IRR onlyRADB 672 100% 67
183.137.128.0/17 Valid Other IRR onlyRADB 672 100% 67
36.21.128.0/17 Valid Other IRR onlyRADB 671 100% 67
36.28.128.0/17 Valid Other IRR onlyRADB 671 100% 67
240e:1c7:20::/44 Valid Other IRR onlyRADB 636 100% 68
240e:471::/32 Valid Other IRR onlyRADB 636 100% 68
240e:473:ff01::/48 Valid Other IRR onlyRADB 636 100% 68
240e:473:fffe::/48 Valid Other IRR onlyRADB 636 100% 68
240e:870:40::/44 Valid Other IRR onlyRADB 636 100% 67
240e:871:10::/44 Valid Other IRR onlyRADB 636 100% 68
240e:471:eeec::/48 Valid Other IRR onlyRADB 635 100% 68
240e:471:eeed::/48 Valid Other IRR onlyRADB 635 100% 68

AS-SET

AS140486 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 14 are in fix.csv.

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR60.163.66.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR115.220.65.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR115.233.186.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR183.137.128.0/17Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR36.21.128.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR36.28.128.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR240e:1c7:20::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:471::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:473:ff01::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:473:fffe::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:870:40::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:871:10::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:471:eeec::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR240e:471:eeed::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS140486 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.