bgpreport

Network · data from 2026-11-12

AS134760 ChinaNet-Hebei-Shijiazhuang-IDC - Shijiazhuang IDC network, CHINANET Hebei province

Registry name: ChinaNet-Hebei-Shijiazhuang-IDC - Shijiazhuang IDC network, CHINANET Hebei province, CN · not in PeeringDB

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

Announced routes

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

103.41.2.0/23 Valid None 672 100% 67
101.96.144.0/20 Valid Other IRR onlyRADB 672 100% 67
103.41.0.0/23 Valid Other IRR onlyRADB 672 100% 67
103.41.164.0/22 Valid Other IRR onlyRADB 672 100% 67
103.143.18.0/23 Valid Other IRR onlyRADB 672 100% 67
103.149.244.0/23 Valid Other IRR onlyRADB 672 100% 67
103.149.246.0/23 Valid Other IRR onlyRADB 672 100% 67
203.55.30.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.93.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.101.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.109.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.110.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.119.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.146.0/23 Valid Other IRR onlyRADB 672 100% 67
203.55.192.0/24 Valid Other IRR onlyRADB 672 100% 67
203.55.218.0/23 Valid Other IRR onlyRADB 672 100% 67
203.56.172.0/23 Valid Other IRR onlyRADB 672 100% 67
203.56.208.0/23 Valid Other IRR onlyRADB 672 100% 67
203.57.61.0/24 Valid Other IRR onlyRADB 672 100% 67
43.250.32.0/22 Valid Other IRR onlyRADB 669 99% 67
103.143.16.0/23 Valid Other IRR onlyRADB 669 99% 67
240e:108:2f::/48 Valid Other IRR onlyRADB 636 100% 68
240e:108:10f0::/48 Valid Other IRR onlyRADB 636 100% 68
240e:980:2f00::/40 Valid Other IRR onlyRADB 636 100% 68
240e:981:f000::/40 Valid Other IRR onlyRADB 636 100% 68
27.185.4.0/22 Valid Other IRR onlyRADB 34 5%low visibility 18
27.185.192.0/18 Valid Other IRR onlyRADB 34 5%low visibility 18
106.119.168.0/21 Valid Other IRR onlyRADB 34 5%low visibility 18
106.119.176.0/21 Valid Other IRR onlyRADB 34 5%low visibility 18
124.236.0.0/17 Valid Other IRR onlyRADB 34 5%low visibility 18
124.239.158.0/23 Valid Other IRR onlyRADB 34 5%low visibility 18
124.239.161.0/24 Valid Other IRR onlyRADB 34 5%low visibility 18
124.239.162.0/23 Valid Other IRR onlyRADB 34 5%low visibility 18
219.148.34.0/24 Valid Other IRR onlyRADB 34 5%low visibility 18
240e:c:800::/37 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:4c::/37 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:b1:8800::/37 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:108:10f3::/48 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:108:10f4::/48 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:100::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:8000::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:8100::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:c000::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:c100::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:e000::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:940:e100::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:981:f300::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
240e:981:f400::/40 Valid Other IRR onlyRADB 25 4%low visibility 15
106.119.160.0/21 Valid Other IRR onlyRADB 12 2%low visibility 8

AS-SET

AS134760 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 52 are in fix.csv.

  • Route object: none1
  • Route object: RIR49
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none103.41.2.0/23No route object for it. Add a route object with origin AS134760 in the RIR database for the space.672 of 673
Route object: RIR101.96.144.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.41.0.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.41.164.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.143.18.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.149.244.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.149.246.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.30.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.93.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.101.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.109.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.110.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.146.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.192.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.55.218.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.56.172.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.56.208.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.57.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR43.250.32.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.143.16.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR240e:108:2f::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:108:10f0::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:980:2f00::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR240e:981:f000::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR27.185.4.0/22Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR27.185.192.0/18Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR106.119.168.0/21Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR106.119.176.0/21Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR124.236.0.0/17Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR124.239.158.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR124.239.161.0/24Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR124.239.162.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR219.148.34.0/24Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR240e:c:800::/37Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:4c::/37Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:b1:8800::/37Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:108:10f3::/48Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:108:10f4::/48Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:100::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:8000::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:8100::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:c000::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:c100::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:e000::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:940:e100::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:981:f300::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR240e:981:f400::/40Route object only in RADB. Add it in the RIR database for the space.25 of 636
Route object: RIR106.119.160.0/21Route object only in RADB. Add it in the RIR database for the space.12 of 673

Route objects not announced

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

103.41.2.0/24RADBValid
103.41.3.0/24RADBValid

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.