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
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% |
| 125.72.138.0/24 | Invalid: origin | None | 125 19% |
| 220.154.116.0/24 | No ROA | None | 654 97% |
| 220.154.117.0/24 | No ROA | None | 654 97% |
| 110.166.64.0/20 | Valid | None | 672 100% |
| 110.167.163.0/24 | Valid | None | 672 100% |
| 110.167.164.0/24 | Valid | None | 672 100% |
| 110.167.255.0/24 | Valid | None | 672 100% |
| 118.213.88.0/24 | Valid | None | 672 100% |
| 118.213.92.0/24 | Valid | None | 672 100% |
| 118.213.141.0/24 | Valid | None | 672 100% |
| 118.213.220.0/24 | Valid | None | 672 100% |
| 125.72.18.0/23 | Valid | None | 672 100% |
| 125.72.124.0/24 | Valid | None | 672 100% |
| 125.72.126.0/24 | Valid | None | 672 100% |
| 125.72.141.0/24 | Valid | None | 672 100% |
| 125.72.143.0/24 | Valid | None | 672 100% |
| 125.72.144.0/24 | Valid | None | 672 100% |
| 125.72.145.0/24 | Valid | None | 672 100% |
| 125.72.146.0/24 | Valid | None | 672 100% |
| 125.72.147.0/24 | Valid | None | 672 100% |
| 220.167.142.0/23 | Valid | None | 672 100% |
| 220.167.180.0/24 | Valid | None | 672 100% |
| 220.167.181.0/24 | Valid | None | 672 100% |
| 220.167.182.0/24 | Valid | None | 672 100% |
| 223.221.10.0/24 | Valid | None | 671 100% |
| 223.221.162.0/24 | Valid | None | 671 100% |
| 223.221.177.0/24 | Valid | None | 671 100% |
| 223.221.179.0/24 | Valid | None | 671 100% |
| 223.221.216.0/24 | Valid | None | 671 100% |
| 240e:981:7101::/48 | Valid | None | 636 100% |
| 240e:981:7102::/48 | Valid | None | 636 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 118.213.93.0/24 | ROAs covering it name AS140061, not AS59223. If AS59223 should announce it, add a ROA for AS59223. |
| Route object: none | 118.213.93.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| ROA: origin | 125.72.138.0/24 | ROAs covering it name AS4134, AS140061, not AS59223. If AS59223 should announce it, add a ROA for AS59223. |
| Route object: none | 125.72.138.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| ROA: none | 220.154.116.0/24 | No ROA covers it. Add a ROA for AS59223, maxLength 24. |
| Route object: none | 220.154.116.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| ROA: none | 220.154.117.0/24 | No ROA covers it. Add a ROA for AS59223, maxLength 24. |
| Route object: none | 220.154.117.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 110.166.64.0/20 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 110.167.163.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 110.167.164.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 110.167.255.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 118.213.88.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 118.213.92.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 118.213.141.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 118.213.220.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.18.0/23 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.124.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.126.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.141.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.143.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.144.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.145.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.146.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 125.72.147.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 220.167.142.0/23 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 220.167.180.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 220.167.181.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 220.167.182.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 223.221.10.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 223.221.162.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 223.221.177.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 223.221.179.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 223.221.216.0/24 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 240e:981:7101::/48 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
| Route object: none | 240e:981:7102::/48 | No route object for it. Add a route object with origin AS59223 in the RIR database for the space. |
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.