bgpreport

Network · data from 2026-11-12

AS132153 CT-SHANXI-MAN-2 - No.3,Shu-Ma Road

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132153, 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.
223.9.200.0/21 Invalid: origin None 125 19% 51
113.25.244.0/24 Valid Other IRR onlyRADB 672 100% 67
223.15.232.0/21 Valid Other IRR onlyRADB 671 100% 67
223.15.240.0/21 Valid Other IRR onlyRADB 671 100% 67
223.15.248.0/22 Valid Other IRR onlyRADB 671 100% 67
223.15.224.0/21 Valid Other IRR onlyRADB 668 99% 67
240e:108:1080::/48 Valid Other IRR onlyRADB 636 100% 67
240e:924:4000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:925:3000::/36 Valid Other IRR onlyRADB 636 100% 68
240e:981:8000::/40 Valid Other IRR onlyRADB 636 100% 67

AS-SET

AS132153 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.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: origin223.9.200.0/21ROAs covering it name AS4134, not AS132153. If AS132153 should announce it, add a ROA for AS132153.125 of 673
Route object: none223.9.200.0/21No route object for it. Add a route object with origin AS132153 in the RIR database for the space.125 of 673
Route object: RIR113.25.244.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR223.15.232.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR223.15.240.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR223.15.248.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR223.15.224.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR240e:108:1080::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:924:4000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:925:3000::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:981:8000::/40Route 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 AS132153 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.