bgpreport

Network · data from 2026-11-12

AS59223 CT-Qinghai-IDC - CHINANET Qinghai province IDC network

Registry name: CT-Qinghai-IDC - CHINANET Qinghai province IDC network, CN · not in PeeringDB

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

Announced routes

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

118.213.93.0/24 Invalid: origin None 125 19% 51
125.72.138.0/24 Invalid: origin None 125 19% 51
220.154.116.0/24 No ROA None 654 97% 67
220.154.117.0/24 No ROA None 654 97% 67
110.166.64.0/20 Valid None 672 100% 67
110.167.163.0/24 Valid None 672 100% 67
110.167.164.0/24 Valid None 672 100% 67
110.167.255.0/24 Valid None 672 100% 67
118.213.88.0/24 Valid None 672 100% 67
118.213.92.0/24 Valid None 672 100% 67
118.213.141.0/24 Valid None 672 100% 67
118.213.220.0/24 Valid None 672 100% 67
125.72.18.0/23 Valid None 672 100% 67
125.72.124.0/24 Valid None 672 100% 67
125.72.126.0/24 Valid None 672 100% 67
125.72.141.0/24 Valid None 672 100% 67
125.72.143.0/24 Valid None 672 100% 67
125.72.144.0/24 Valid None 672 100% 67
125.72.145.0/24 Valid None 672 100% 67
125.72.146.0/24 Valid None 672 100% 67
125.72.147.0/24 Valid None 672 100% 67
220.167.142.0/23 Valid None 672 100% 67
220.167.180.0/24 Valid None 672 100% 67
220.167.181.0/24 Valid None 672 100% 67
220.167.182.0/24 Valid None 672 100% 67
223.221.10.0/24 Valid None 671 100% 67
223.221.162.0/24 Valid None 671 100% 67
223.221.177.0/24 Valid None 671 100% 67
223.221.179.0/24 Valid None 671 100% 67
223.221.216.0/24 Valid None 671 100% 67
240e:981:7101::/48 Valid None 636 100% 68
240e:981:7102::/48 Valid None 636 100% 68

AS-SET

AS59223 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 36 are in fix.csv.

  • ROA: origin2
  • ROA: none2
  • Route object: none32
ChangePrefix or setDetailFull-table peers
ROA: origin118.213.93.0/24ROAs covering it name AS140061, not AS59223. If AS59223 should announce it, add a ROA for AS59223.125 of 673
Route object: none118.213.93.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.125 of 673
ROA: origin125.72.138.0/24ROAs covering it name AS4134, AS140061, not AS59223. If AS59223 should announce it, add a ROA for AS59223.125 of 673
Route object: none125.72.138.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.125 of 673
ROA: none220.154.116.0/24No ROA covers it. Add a ROA for AS59223, maxLength 24.654 of 673
Route object: none220.154.116.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.654 of 673
ROA: none220.154.117.0/24No ROA covers it. Add a ROA for AS59223, maxLength 24.654 of 673
Route object: none220.154.117.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.654 of 673
Route object: none110.166.64.0/20No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none110.167.163.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none110.167.164.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none110.167.255.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none118.213.88.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none118.213.92.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none118.213.141.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none118.213.220.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.18.0/23No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.124.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.126.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.141.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.143.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.144.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.145.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.146.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none125.72.147.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none220.167.142.0/23No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none220.167.180.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none220.167.181.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none220.167.182.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.672 of 673
Route object: none223.221.10.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.671 of 673
Route object: none223.221.162.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.671 of 673
Route object: none223.221.177.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.671 of 673
Route object: none223.221.179.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.671 of 673
Route object: none223.221.216.0/24No route object for it. Add a route object with origin AS59223 in the RIR database for the space.671 of 673
Route object: none240e:981:7101::/48No route object for it. Add a route object with origin AS59223 in the RIR database for the space.636 of 636
Route object: none240e:981:7102::/48No route object for it. Add a route object with origin AS59223 in the RIR database for the space.636 of 636

Route objects not announced

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