bgpreport

Network · data from 2026-11-12

AS140484 CHINATELECOM-ZHEJIANG-SHENGJI-EPCCE-NETWORK - CHINATELECOM ZHEJIANG province Shengji EPCCE network

Registry name: CHINATELECOM-ZHEJIANG-SHENGJI-EPCCE-NETWORK - CHINATELECOM ZHEJIANG province Shengji EPCCE network, CN · not in PeeringDB

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

Announced routes

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

115.228.133.0/24 Valid None 672 100% 67
115.228.137.0/24 Valid Other IRR onlyRADB 672 100% 67
115.228.138.0/23 Valid Other IRR onlyRADB 672 100% 67
115.228.140.0/22 Valid Other IRR onlyRADB 672 100% 67
115.228.134.0/24 Valid Other IRR onlyRADB 2 0%low visibility 1
115.228.135.0/24 Valid Other IRR onlyRADB 2 0%low visibility 1
115.228.136.0/24 Valid Other IRR onlyRADB 2 0%low visibility 1

AS-SET

AS140484 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 29 are in fix.csv.

  • Route object: none1
  • Route object: RIR6
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
Route object: none115.228.133.0/24No route object for it. Add a route object with origin AS140484 in the RIR database for the space.672 of 673
Route object: RIR115.228.137.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR115.228.138.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR115.228.140.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR115.228.134.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR115.228.135.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR115.228.136.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

125.122.12.0/23RADBValid
125.122.14.0/23RADBValid
125.122.32.0/23RADBValid
125.122.34.0/23RADBValid
125.122.36.0/23RADBValid
125.122.38.0/23RADBValid
125.122.86.0/23RADBValid
125.122.90.0/23RADBValid
125.122.96.0/23RADBValid
125.122.98.0/23RADBValid
125.122.100.0/23RADBValid
125.122.102.0/23RADBValid
125.122.116.0/23RADBValid
125.122.118.0/23RADBValid
125.122.120.0/23RADBValid
125.122.128.0/23RADBValid
125.122.130.0/23RADBValid
125.122.132.0/23RADBValid
125.122.134.0/23RADBValid
125.122.152.0/23RADBValid
125.122.154.0/23RADBValid
125.122.156.0/23RADBValid

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.