bgpreport

Network · data from 2026-11-12

AS132536 CHINANET-TIANJIN-MAN-NEW - China Telecom

Registry name: CHINANET-TIANJIN-MAN-NEW - China Telecom, CN · not in PeeringDB

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

Announced routes

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

42.122.194.0/24 No ROA None 672 100% 67
42.122.196.0/24 No ROA None 672 100% 67
103.116.139.0/24 Valid None 672 100% 67
42.122.16.0/22 Valid Other IRR onlyRADB 672 100% 67
42.122.20.0/23 Valid Other IRR onlyRADB 672 100% 67
42.122.22.0/24 Valid Other IRR onlyRADB 672 100% 67
42.122.23.0/24 Valid Other IRR onlyRADB 672 100% 67
43.225.255.0/24 Valid Other IRR onlyRADB 672 100% 67
123.150.228.0/23 Valid Other IRR onlyRADB 672 100% 67
123.151.124.0/24 Valid Other IRR onlyRADB 672 100% 67
123.151.165.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.24.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.25.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.31.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.33.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.34.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.35.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.43.0/24 Valid Other IRR onlyRADB 672 100% 67
180.213.77.0/24 Valid Other IRR onlyRADB 672 100% 67
123.151.20.0/24 Valid Other IRR onlyRADB 666 99% 67
240e:981:9203::/48 Valid Other IRR onlyRADB 636 100% 67
240e:981:9204::/48 Valid Other IRR onlyRADB 636 100% 67
240e:981:9205::/48 Valid Other IRR onlyRADB 636 100% 67
240e:983:904::/48 Valid Other IRR onlyRADB 636 100% 67

AS-SET

AS132536 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 26 are in fix.csv.

  • ROA: none2
  • Route object: none3
  • Route object: RIR21
ChangePrefix or setDetailFull-table peers
ROA: none42.122.194.0/24No ROA covers it. Add a ROA for AS132536, maxLength 24.672 of 673
Route object: none42.122.194.0/24No route object for it. Add a route object with origin AS132536 in the RIR database for the space.672 of 673
ROA: none42.122.196.0/24No ROA covers it. Add a ROA for AS132536, maxLength 24.672 of 673
Route object: none42.122.196.0/24No route object for it. Add a route object with origin AS132536 in the RIR database for the space.672 of 673
Route object: none103.116.139.0/24No route object for it. Add a route object with origin AS132536 in the RIR database for the space.672 of 673
Route object: RIR42.122.16.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.122.20.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.122.22.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR42.122.23.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.225.255.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR123.150.228.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR123.151.124.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR123.151.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.24.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.25.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.33.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.34.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.35.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.43.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR180.213.77.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR123.151.20.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR240e:981:9203::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:981:9204::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:981:9205::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:983:904::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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