bgpreport

Network · data from 2026-11-12

AS132147 CT-SHANXI-MAN - No.3,Shu-Ma Road

Registry name: CT-SHANXI-MAN - No.3,Shu-Ma Road, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132147, 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.
1.71.16.0/20 Valid Other IRR onlyRADB 672 100% 67
1.71.64.0/20 Valid Other IRR onlyRADB 672 100% 67
1.71.144.0/21 Valid Other IRR onlyRADB 672 100% 67
1.71.160.0/21 Valid Other IRR onlyRADB 672 100% 67
59.49.40.0/21 Valid Other IRR onlyRADB 672 100% 67
59.49.80.0/20 Valid Other IRR onlyRADB 672 100% 67
59.49.117.0/24 Valid Other IRR onlyRADB 672 100% 67
1.71.152.0/21 Valid Other IRR onlyRADB 671 100% 67
240e:4:e000::/40 Valid Other IRR onlyRADB 636 100% 68
240e:924::/36 Valid Other IRR onlyRADB 636 100% 68
240e:925::/36 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS132147 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 11 are in fix.csv.

  • Route object: RIR11
ChangePrefix or setDetailFull-table peers
Route object: RIR1.71.16.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.71.64.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.71.144.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.71.160.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR59.49.40.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR59.49.80.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR59.49.117.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR1.71.152.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR240e:4:e000::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:924::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:925::/36Route 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 AS132147 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.