Network · data from 2026-11-12
AS23853 SHUXUN
Registry name: CNNIC-DSNET-AP - Shanghai Data Solution Co., Ltd., CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23853, 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.
| 211.147.72.0/21 | Valid | Nonecovered by 211.147.64.0/19 | 673 100% |
| 211.147.95.0/24 | Valid | Nonecovered by 211.147.88.0/21 | 673 100% |
| 120.136.133.0/24 | Valid | Nonecovered by 120.136.132.0/23 | 672 100% |
| 120.136.140.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.141.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.142.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.143.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.144.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.145.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.146.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.147.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.148.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.149.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.150.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.151.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.152.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.153.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.154.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.155.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.180.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.181.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.182.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.183.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.184.0/22 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.188.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.189.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.190.0/24 | Valid | Nonecovered by 120.136.128.0/18 | 78 12% |
| 120.136.128.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 120.136.128.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 120.136.128.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 120.136.130.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 120.136.132.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 120.136.132.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 120.136.134.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.208.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.208.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.208.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.209.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 211.144.210.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.212.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.212.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.214.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.214.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.216.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.216.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.216.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.216.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.218.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.219.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.220.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.220.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.221.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.144.222.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.64.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.64.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.65.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.66.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.67.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.68.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.69.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.70.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.71.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.72.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.73.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.74.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.75.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.76.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.77.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.78.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.80.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.80.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.81.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.82.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.83.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.84.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.86.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.87.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.88.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.88.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.89.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.90.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.91.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.92.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.92.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.93.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 211.147.94.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 2404:7600::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:7600:100::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS23853's PeeringDB record names no 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 43 are in fix.csv.
- Route object: none27
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 211.147.72.0/21 | No route object for it. A route object for 211.147.64.0/19 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 211.147.95.0/24 | No route object for it. A route object for 211.147.88.0/21 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.133.0/24 | No route object for it. A route object for 120.136.132.0/23 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.140.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.141.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.142.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.143.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.144.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.145.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.146.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.147.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.148.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.149.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.150.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.151.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.152.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.153.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.154.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.155.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.180.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.181.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.182.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.183.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.184.0/22 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.188.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.189.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
| Route object: none | 120.136.190.0/24 | No route object for it. A route object for 120.136.128.0/18 with origin AS23853 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23853 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23853 whose prefix no peer sees AS23853 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 120.136.128.0/18 | APNIC | No ROA |
| 120.136.160.0/21 | APNIC | Invalid: origin |
| 211.144.208.0/20 | APNIC | Valid |
| 211.144.208.0/24 | APNIC | Valid |
| 211.144.210.0/24 | APNIC | Valid |
| 211.144.211.0/24 | APNIC | Valid |
| 211.144.212.0/24 | APNIC | Valid |
| 211.144.213.0/24 | APNIC | Valid |
| 211.144.215.0/24 | APNIC | Valid |
| 211.144.217.0/24 | APNIC | Valid |
| 211.144.218.0/24 | APNIC | Valid |
| 211.144.220.0/24 | APNIC | Valid |
| 211.144.222.0/24 | APNIC | Valid |
| 211.144.223.0/24 | APNIC | Valid |
| 211.147.64.0/19 | APNIC | No ROA |
| 211.147.79.0/24 | APNIC | Valid |
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.