bgpreport

Network · data from 2026-11-12

AS152120 UNICOM-TJGC-IDC - China Unicom TianJing GaoCun IDC network

Registry name: UNICOM-TJGC-IDC - China Unicom TianJing GaoCun IDC network, CN · not in PeeringDB

12IPv4 routes 100.0% RPKI valid · 25.0% with a route object
11IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 20 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS152120, seen from no peer

Announced routes

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

60.24.140.0/22 Valid None 673 100% 67
60.24.144.0/22 Valid None 673 100% 67
60.24.148.0/22 Valid None 673 100% 67
60.24.152.0/22 Valid None 673 100% 67
60.24.156.0/22 Valid None 673 100% 67
60.24.160.0/22 Valid None 673 100% 67
60.24.164.0/22 Valid None 673 100% 67
60.24.168.0/22 Valid None 673 100% 67
117.8.188.0/24 Valid None 673 100% 67
2408:8000:2014::/48 Valid None 629 99% 67
2408:8000:2015::/48 Valid None 629 99% 67
2408:8710:6010::/48 Valid None 629 99% 67
2408:8710:6020::/46 Valid None 629 99% 67
2408:8710:6024::/46 Valid None 629 99% 67
2408:8710:6028::/46 Valid None 629 99% 67
2408:8710:602c::/46 Valid None 629 99% 67
2408:8710:6030::/46 Valid None 629 99% 67
2408:8710:6034::/46 Valid None 629 99% 67
2408:8710:6038::/46 Valid None 629 99% 67
2408:8710:603c::/46 Valid None 629 99% 67
116.130.23.0/24 Valid Other IRR onlyRADB 673 100% 67
116.130.24.0/24 Valid Other IRR onlyRADB 673 100% 67
116.130.25.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS152120 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 23 are in fix.csv.

  • Route object: none20
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
Route object: none60.24.140.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.144.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.148.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.152.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.156.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.160.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.164.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none60.24.168.0/22No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none117.8.188.0/24No route object for it. Add a route object with origin AS152120 in the RIR database for the space.673 of 673
Route object: none2408:8000:2014::/48No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8000:2015::/48No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6010::/48No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6020::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6024::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6028::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:602c::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6030::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6034::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:6038::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: none2408:8710:603c::/46No route object for it. Add a route object with origin AS152120 in the RIR database for the space.629 of 636
Route object: RIR116.130.23.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.130.24.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.130.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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