bgpreport

Network · data from 2026-11-12

AS141739 CT-CHONGQING-MAN2-AP - China Telecom

Registry name: CT-CHONGQING-MAN2-AP - China Telecom, CN · not in PeeringDB

37IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
20Route objects not announced registered with origin AS141739, seen from no peer

Announced routes

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

106.80.120.0/21 Valid Other IRR onlyRADB 672 100% 67
106.80.176.0/20 Valid Other IRR onlyRADB 672 100% 67
106.89.48.0/20 Valid Other IRR onlyRADB 672 100% 67
106.89.64.0/20 Valid Other IRR onlyRADB 672 100% 67
113.248.96.0/20 Valid Other IRR onlyRADB 672 100% 67
113.248.160.0/19 Valid Other IRR onlyRADB 672 100% 67
113.248.208.0/21 Valid Other IRR onlyRADB 672 100% 67
113.248.216.0/21 Valid Other IRR onlyRADB 672 100% 67
113.248.224.0/19 Valid Other IRR onlyRADB 672 100% 67
113.249.32.0/20 Valid Other IRR onlyRADB 672 100% 67
113.249.224.0/20 Valid Other IRR onlyRADB 672 100% 67
113.250.128.0/20 Valid Other IRR onlyRADB 672 100% 67
113.250.144.0/21 Valid Other IRR onlyRADB 672 100% 67
113.251.208.0/21 Valid Other IRR onlyRADB 672 100% 67
113.251.224.0/21 Valid Other IRR onlyRADB 672 100% 67
113.251.248.0/21 Valid Other IRR onlyRADB 672 100% 67
125.85.64.0/18 Valid Other IRR onlyRADB 672 100% 67
125.85.128.0/19 Valid Other IRR onlyRADB 672 100% 67
14.107.160.0/22 Valid Other IRR onlyRADB 671 100% 67
14.107.172.0/22 Valid Other IRR onlyRADB 671 100% 67
14.107.176.0/21 Valid Other IRR onlyRADB 671 100% 67
14.110.80.0/20 Valid Other IRR onlyRADB 671 100% 67
14.110.120.0/21 Valid Other IRR onlyRADB 671 100% 67
125.80.76.0/22 Valid Other IRR onlyRADB 664 99% 67
125.80.108.0/22 Valid Other IRR onlyRADB 664 99% 67
125.80.152.0/21 Valid Other IRR onlyRADB 664 99% 67
125.80.192.0/19 Valid Other IRR onlyRADB 664 99% 67
125.80.248.0/21 Valid Other IRR onlyRADB 664 99% 67
125.81.232.0/21 Valid Other IRR onlyRADB 664 99% 67
125.84.232.0/22 Valid Other IRR onlyRADB 664 99% 67
125.86.0.0/20 Valid Other IRR onlyRADB 664 99% 67
125.86.16.0/20 Valid Other IRR onlyRADB 664 99% 67
125.86.84.0/22 Valid Other IRR onlyRADB 664 99% 67
125.86.128.0/22 Valid Other IRR onlyRADB 664 99% 67
125.86.132.0/22 Valid Other IRR onlyRADB 664 99% 67
125.86.136.0/21 Valid Other IRR onlyRADB 664 99% 67
125.87.148.0/22 Valid Other IRR onlyRADB 664 99% 67

AS-SET

AS141739 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 57 are in fix.csv.

  • Route object: RIR37
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: RIR106.80.120.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR106.80.176.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR106.89.48.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR106.89.64.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.248.96.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.248.160.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.248.208.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.248.216.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.248.224.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.249.32.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.249.224.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.250.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.250.144.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.251.208.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.251.224.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR113.251.248.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR125.85.64.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR125.85.128.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR14.107.160.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR14.107.172.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR14.107.176.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR14.110.80.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR14.110.120.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR125.80.76.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.80.108.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.80.152.0/21Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.80.192.0/19Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.80.248.0/21Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.81.232.0/21Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.84.232.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.86.0.0/20Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.86.16.0/20Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.86.84.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.86.128.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.86.132.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.86.136.0/21Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR125.87.148.0/22Route object only in RADB. Add it in the RIR database for the space.664 of 673

Route objects not announced

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

113.248.0.0/18RADBValid
113.248.64.0/19RADBValid
113.249.0.0/19RADBValid
113.251.64.0/19RADBValid
125.80.80.0/20RADBValid
125.80.112.0/20RADBValid
125.83.0.0/21RADBValid
125.83.48.0/20RADBValid
125.83.240.0/21RADBValid
125.84.120.0/22RADBValid
125.84.196.0/22RADBValid
125.84.200.0/22RADBValid
125.85.0.0/19RADBValid
125.87.200.0/21RADBValid
240e:188:5a0::/48RADBNo ROA
240e:188:5a1::/48RADBNo ROA
240e:188:5a2::/48RADBNo ROA
240e:188:15a0::/48RADBNo ROA
240e:188:15a1::/48RADBNo ROA
240e:188:15a2::/48RADBNo 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.