bgpreport

Network · data from 2026-11-12

AS140494 CHINATELECOM-ZHEJIANG-HUZHOU-5G-NETWORK - CHINATELECOM ZHEJIANG province HUZHOU 5G network

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

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

Announced routes

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

240e:691:5b03::/48 Invalid: origin None 78 12% 42
240e:690:5a02::/48 Invalid: origin None 77 12% 42
240e:691:5a02::/48 Invalid: origin None 77 12% 42
240e:691:5a03::/48 Invalid: origin None 77 12% 42
240e:691:5b02::/48 Invalid: origin None 77 12% 42
240e:696:5528::/48 Invalid: origin None 77 12% 42
240e:690:5b07::/48 Valid None 636 100% 67
240e:693:5702::/48 Valid None 636 100% 67
240e:695:5502::/48 Valid None 636 100% 67
240e:390:5540::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5550::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5560::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5570::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5580::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5590::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5d00::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5d10::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5d20::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5d30::/44 Valid Other IRR onlyRADB 636 100% 67
240e:390:5d40::/44 Valid Other IRR onlyRADB 636 100% 67
240e:690:5603::/48 Valid Other IRR onlyRADB 636 100% 67
240e:690:5b02::/48 Valid Other IRR onlyRADB 636 100% 67
240e:690:5b03::/48 Valid Other IRR onlyRADB 636 100% 67
240e:690:5b06::/48 Valid Other IRR onlyRADB 636 100% 67
240e:691:5902::/48 Valid Other IRR onlyRADB 636 100% 67
240e:691:5c02::/48 Valid Other IRR onlyRADB 636 100% 67
240e:693:5703::/48 Valid Other IRR onlyRADB 636 100% 67
240e:693:5704::/48 Valid Other IRR onlyRADB 636 100% 67
240e:696:5522::/48 Valid Other IRR onlyRADB 636 100% 67
240e:696:5525::/48 Valid Other IRR onlyRADB 636 100% 67
240e:695:5402::/48 Valid Other IRR onlyRADB 634 100% 67

AS-SET

AS140494 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 37 are in fix.csv.

  • ROA: origin6
  • Route object: none9
  • Route object: RIR22
ChangePrefix or setDetailFull-table peers
ROA: origin240e:691:5b03::/48ROAs covering it name AS4134, not AS140494. If AS140494 should announce it, add a ROA for AS140494.78 of 636
Route object: none240e:691:5b03::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.78 of 636
ROA: origin240e:690:5a02::/48ROAs covering it name AS4134, not AS140494. If AS140494 should announce it, add a ROA for AS140494.77 of 636
Route object: none240e:690:5a02::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.77 of 636
ROA: origin240e:691:5a02::/48ROAs covering it name AS4134, not AS140494. If AS140494 should announce it, add a ROA for AS140494.77 of 636
Route object: none240e:691:5a02::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.77 of 636
ROA: origin240e:691:5a03::/48ROAs covering it name AS4134, not AS140494. If AS140494 should announce it, add a ROA for AS140494.77 of 636
Route object: none240e:691:5a03::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.77 of 636
ROA: origin240e:691:5b02::/48ROAs covering it name AS4134, not AS140494. If AS140494 should announce it, add a ROA for AS140494.77 of 636
Route object: none240e:691:5b02::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.77 of 636
ROA: origin240e:696:5528::/48ROAs covering it name AS4134, not AS140494. If AS140494 should announce it, add a ROA for AS140494.77 of 636
Route object: none240e:696:5528::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.77 of 636
Route object: none240e:690:5b07::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.636 of 636
Route object: none240e:693:5702::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.636 of 636
Route object: none240e:695:5502::/48No route object for it. Add a route object with origin AS140494 in the RIR database for the space.636 of 636
Route object: RIR240e:390:5540::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5550::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5560::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5570::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5580::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5590::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5d00::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5d10::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5d20::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5d30::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:390:5d40::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:690:5603::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:690:5b02::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:690:5b03::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:690:5b06::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:691:5902::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:691:5c02::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:693:5703::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:693:5704::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:696:5522::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:696:5525::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:695:5402::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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