bgpreport

Network · data from 2026-11-12

AS137688 CHINATELECOM-Liaoning-Benxi-MAN - CHINATELECOM Liaoning Benxi MAN

Registry name: CHINATELECOM-Liaoning-Benxi-MAN - CHINATELECOM Liaoning Benxi MAN, CN · not in PeeringDB

13IPv4 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
13Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS137688, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS137688, 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.
123.177.12.0/23 Valid Other IRR onlyRADB 28 4%low visibility 16
42.202.24.0/21 Valid Other IRR onlyRADB 25 4%low visibility 15
42.203.224.0/19 Valid Other IRR onlyRADB 25 4%low visibility 15
59.45.64.0/19 Valid Other IRR onlyRADB 25 4%low visibility 15
59.47.0.0/20 Valid Other IRR onlyRADB 25 4%low visibility 15
59.47.192.0/19 Valid Other IRR onlyRADB 25 4%low visibility 15
59.47.224.0/20 Valid Other IRR onlyRADB 25 4%low visibility 15
123.186.144.0/20 Valid Other IRR onlyRADB 25 4%low visibility 15
123.245.192.0/20 Valid Other IRR onlyRADB 25 4%low visibility 15
123.246.96.0/20 Valid Other IRR onlyRADB 25 4%low visibility 15
182.202.128.0/19 Valid Other IRR onlyRADB 25 4%low visibility 15
182.202.160.0/19 Valid Other IRR onlyRADB 25 4%low visibility 15
219.149.32.0/21 Valid Other IRR onlyRADB 25 4%low visibility 15

AS-SET

AS137688 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 40 are in fix.csv.

  • Route object: RIR13
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
Route object: RIR123.177.12.0/23Route object only in RADB. Add it in the RIR database for the space.28 of 673
Route object: RIR42.202.24.0/21Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR42.203.224.0/19Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR59.45.64.0/19Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR59.47.0.0/20Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR59.47.192.0/19Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR59.47.224.0/20Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR123.186.144.0/20Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR123.245.192.0/20Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR123.246.96.0/20Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR182.202.128.0/19Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR182.202.160.0/19Route object only in RADB. Add it in the RIR database for the space.25 of 673
Route object: RIR219.149.32.0/21Route object only in RADB. Add it in the RIR database for the space.25 of 673

Route objects not announced

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

240e:1:a000::/37RADBValid
240e:86:3000::/37RADBValid
240e:30c:4a00::/39RADBValid
240e:30c:4c00::/38RADBValid
240e:30c:5000::/38RADBValid
240e:30c:5400::/39RADBValid
240e:30d:4a00::/39RADBValid
240e:30d:4c00::/38RADBValid
240e:30d:5000::/38RADBValid
240e:30d:5400::/39RADBValid
240e:30e:4a00::/39RADBValid
240e:30e:4c00::/38RADBValid
240e:30e:5000::/38RADBValid
240e:30e:5400::/39RADBValid
240e:30f:4a00::/39RADBValid
240e:30f:4c00::/38RADBValid
240e:30f:5000::/38RADBValid
240e:30f:5400::/39RADBValid
240e:60c:6000::/36RADBValid
240e:60c:b000::/37RADBValid
240e:60c:d800::/38RADBValid
240e:60c:f800::/38RADBValid
240e:90d:a000::/36RADBValid
240e:90d:d000::/37RADBValid
240e:90d:f000::/37RADBValid
240e:90e:2000::/36RADBValid
240e:981:240d::/48RADBValid

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.