Data as of Nov 13, 2026
210.22.192.0/18
9 residential-proxy exits · 30 daysCHINA UNICOM Industrial Internet Backbone · space held by China Unicom IP network
Residential-proxy exits
Proxy exits
9
0.05% of its addresses · 30 days
Always-on exits
1
11% of its exits
Spread
1 of 64
/24s with at least one exit
Providers
33
selling exits here
Oct 14, 2026 – Nov 12, 2026
Exits seen per day
1.9K observations
Proxy providers listing exits
- 2Captcha
- Ake.net
- BartProxies
- BirdProxies
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- FlashProxy
- FlexyProxies
- GSocks
- Geonix
- GonzoProxy
- IPOasis
- IPPeak
- Infatica
- LemonPrime
- LightningProxies
- MangoProxy
- NodeProxy
- NovProxy
- NovaProxy
- PROXYSCRAPE
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- Proxyma
- RainProxy
- Shifter
- VantageProxies
- VibeProxies
- VitalProxy
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 210.22.193.0/24 since May 2005 | AS9929 | Internet provider | China Unicom IP network | ||
| 210.22.195.0/24 since May 2005 | AS9929 | Internet provider | China Unicom IP network | ||
| 210.22.199.0/24 since Apr 2025 | AS4837 | Residential | China Unicom IP network | ||
| 210.22.200.0/24 since May 2005 | AS9929 | Internet provider | China Unicom IP network | ||
| 210.22.206.0/24 since May 2005 | AS9929 | Internet provider | China Unicom IP network | ||
| 210.22.209.0/24 since May 2005 | AS9929 | Internet provider | China Unicom IP network | ||
| 210.22.220.0/22 since May 2017 | AS17621 | Residential | 9 1 always on | China Unicom IP network | |
| 210.22.240.0/21 since Oct 2017 | AS17621 | Residential | China Unicom IP network | ||
| 210.22.240.0/24 since Jan 2022 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.241.0/24 since Jan 2022 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.242.0/24 since Jan 2022 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.243.0/24 since Jan 2022 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.244.0/24 since Jan 2022 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.245.0/24 since Dec 2021 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.246.0/24 since Dec 2021 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.247.0/24 since Dec 2021 | AS140979 | Hosting | China Unicom IP network | ||
| 210.22.248.0/22 since Sep 2017 | AS17621 | Residential | China Unicom IP network | ||
| 210.22.248.0/24 since Aug 2020 | AS17621 | Residential | China Unicom IP network | ||
| 210.22.249.0/24 since Aug 2020 | AS17621 | Residential | China Unicom IP network | ||
| 210.22.252.0/24 since Aug 2020 | AS17621 | Residential | China Unicom IP network | ||
| 210.22.254.0/23 since Oct 2020 | AS17621 | Residential | China Unicom IP network |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 210. | 131,072 | UNICOM-CN | China Unicom IP network | ALLOCATED PORTABLE | — | hqs-ipabuse@ |
| └ 210.22.0.0/16 | 65,536 | UNICOM-CN | China Unicom IP network | ALLOCATED PORTABLE | — | hqs-ipabuse@ |
| └ 210.22.192.0/25 | 128 | XUZHOU-BRANCH | xuzhou branch of CNC,Jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.192.128/26 | 64 | XZ-NETBAR-GROUP | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.192.192/27 | 32 | XUZHOU-NETBAR-GROUP | xuzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.192.224/28 | 16 | shanghai-fangxin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.192.240/28 | 16 | xzdibei-netbar-group | xu zhou city, Jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.0/25 | 128 | YANGZHOU-BRANCH | yangzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.128/26 | 64 | shanghai-fangcheng-xintong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.192/28 | 16 | shanghai-shengchan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.208/28 | 16 | YANGZHOU-JIAOTONG-MANSION | yangzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.224/29 | 8 | YANGZHOU-GUOMAO-MANSION | yangzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.232/29 | 8 | shanghai-senda-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.193.240/28 | 16 | YANGZHOU-JIANGLONG-MANSION | yangzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.194.0/25 | 128 | hangzhou-mini-IDC | hangzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.194.128/25 | 128 | hangzhou-mini-IDC | hangzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.195.0/25 | 128 | suzhou-mini-IDC | suzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.195.128/25 | 128 | suzhou-mini-IDC | suzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.196.0/25 | 128 | shanghai-siyou-fanghui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.196.128/26 | 64 | shanghai-guloudajie-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.196.192/26 | 64 | HUBEI-JUYOU-NETWORK | hubei province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.197.0/25 | 128 | YANGZI-SHIHUA-LTD | nanjing city, jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.197.128/26 | 64 | xuzhou-171 | xuzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.197.192/26 | 64 | shanghai-haiyingdai-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.198.0/25 | 128 | shanghai-hanyong-sijiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.198.128/25 | 128 | shanghai-guochen-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.198.192/26 | 64 | YIGAO-DIGITAL-SQUARE | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via shanghai-guochen-corp |
| └ 210.22.199.0/25 | 128 | jiangsu-zhenjiang-branch | jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.199.128/25 | 128 | jiangsu-zhenjiang-branch | jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.200.0/25 | 128 | jiangsu-zhenjiang-branch2 | jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.200.128/25 | 128 | jiangsu-zhenjiang-branch2 | jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.201.0/25 | 128 | haimen-broadcast-tv | nantong city, jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.201.128/26 | 64 | nantong-medicine-mansion | Nantong city,Jiangsu province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.201.192/27 | 32 | shanghai-chenhong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.201.224/28 | 16 | shanghai-wanghua-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.201.240/28 | 16 | NANTONG-DALUN-HUAGONG-LTD | nantong city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.202.0/25 | 128 | hubei-yichang-branch | yichang city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.202.128/25 | 128 | hubei-yichang-branch | yichang city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.203.0/25 | 128 | hubei-yichang-branch2 | yichang city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.203.128/25 | 128 | hubei-yichang-branch2 | yichang city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.204.0/25 | 128 | hubei-jingzhou-branch | yichang city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.204.128/25 | 128 | hubei-jingzhou-branch | jingzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.205.0/25 | 128 | hubei-jingzhou-branch2 | jingzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.205.128/25 | 128 | hubei-jingzhou-branch2 | jingzhou city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.206.0/26 | 64 | JIANGXI-BCTV-TECH | Jiangxi province broadcast&television technique corp. +86-791-8113772 | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.206.64/27 | 32 | nanchang-borong-electronic | Nanchang city,Jiangxi province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.206.96/27 | 32 | nanchang-gongdian-bureau | jiangxi province | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.206.128/25 | 128 | shanghai-yuqin-yaozong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.206.192/26 | 64 | NANCHANG-NETBAR-GROUP | nanchang city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via shanghai-yuqin-yaozong-corp |
| └ 210. | 512 | xuzhou-branch-bb-users | xuzhou branch of CNC, Jiangsu province | ALLOCATED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.207.192/27 | 32 | shanghai-shijin-yuangui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via xuzhou-branch-bb-users |
| └ 210.22.207.224/28 | 16 | shanghai-longjin-piaoliang | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via xuzhou-branch-bb-users |
| └ 210.22.207.240/28 | 16 | shanghai-jinxiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via xuzhou-branch-bb-users |
| └ 210.22.209.0/24 | 256 | zhenjiang-customer4 | Zhengjiang city, Jiangsu province,China | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.210.0/23 | 512 | Xuzhou-branch-CPN | xuzhou branch of CNC,Jiangsu province | ALLOCATED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.212.0/25 | 128 | shanghai-qingjiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.212.128/25 | 128 | shanghai-kunming-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.213.0/26 | 64 | shanghai-henan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.213.64/26 | 64 | shanghai-shiqing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.213.128/27 | 32 | shanghai-wenjingkui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.213.160/27 | 32 | shanghai-sichuan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.213.192/26 | 64 | shanghai-neimeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.214.0/25 | 128 | shanghai-kunlong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.214.128/25 | 128 | shanghai-longjiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.215.0/25 | 128 | shanghai-woshishui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.215.128/25 | 128 | shanghai-woshishui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.216.0/26 | 64 | shanghai-quanhui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.216.64/26 | 64 | shanghai-huiquan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.216.128/27 | 32 | shanghai-kekuai-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.216.160/27 | 32 | shanghai-huishu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.216.192/26 | 64 | shanghai-fenghui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.217.0/25 | 128 | shanghai-huiyuanjing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.217.128/25 | 128 | shanghai-jingshifeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.218.0/25 | 128 | shanghai-jiushuiguai-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.218.128/25 | 128 | shanghai-jguanli-yijian-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.219.0/25 | 128 | shanghai-jianghui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.219.128/25 | 128 | shanghai-shihui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.220.0/26 | 64 | shanghai-youbang-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.220.64/26 | 64 | shanghai-youshi-quanti-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.220.128/25 | 128 | shanghai-qunfeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.221.0/26 | 64 | shanghai-shiyuan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.221.64/26 | 64 | shanghai-bingxing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.221.128/25 | 128 | shanghai-shuanxing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.222.0/26 | 64 | shanghai-shunchang-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.222.64/26 | 64 | shanghai-tiansu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.222.128/25 | 128 | shanghai-woshui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.223.0/26 | 64 | shanghai-jingshui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.223.64/26 | 64 | shanghai-fangyuan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.223.128/25 | 128 | shanghai-qingjing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.224.0/25 | 128 | shanghai-fangqingshui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.224.128/25 | 128 | shanghai-rengyunjiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.225.0/25 | 128 | shanghai-qingsheng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.225.128/25 | 128 | shanghai-dangran-burang | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.226.0/25 | 128 | shanghai-bili-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.226.128/25 | 128 | shanghai-shirenghui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.227.0/26 | 64 | shanghai-jiaohui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.227.64/26 | 64 | shanghai-huozhe-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.227.128/25 | 128 | shanghai-yunhuo-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.228.0/26 | 64 | shanghai-yihui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.228.64/26 | 64 | shanghai-rengkun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.228.128/25 | 128 | shanghai-huiyan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.229.0/26 | 64 | shanghai-jiuwen-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.229.64/26 | 64 | shanghai-hulin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.229.128/25 | 128 | shanghai-quebao-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.230.0/26 | 64 | shanghai-tongxin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.230.64/26 | 64 | shanghai-daping-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.230.128/25 | 128 | shanghai-xiaoshui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.231.0/25 | 128 | shanghai-cuisong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.231.128/25 | 128 | shanghai-shuihuo-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.232.0/25 | 128 | shanghai-yida-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.232.128/25 | 128 | shanghai-yipiao-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.233.0/25 | 128 | shanghai-rengkuai-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.233.128/25 | 128 | shanghai-youxian-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.234.0/25 | 128 | shanghai-songshu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.234.128/25 | 128 | shanghai-wenjian-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.235.0/25 | 128 | shanghai-shishuo-xinyu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.235.128/25 | 128 | shanghai-xingyu-xingyuan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.236.0/26 | 64 | shanghai-yuandong-fangxin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.236.64/26 | 64 | shanghai-xinghong-xiayu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.236.128/27 | 32 | shanghai-xihan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.236.160/27 | 32 | shanghai-jingjiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.236.192/26 | 64 | shanghai-kailun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.237.0/26 | 64 | shanghai-jiangjun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.237.64/26 | 64 | shanghai-fanghui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.237.128/27 | 32 | shanghai-guaiyi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.237.160/27 | 32 | shanghai-shenqi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.237.192/26 | 64 | shanghai-yueshu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.238.0/26 | 64 | shanghai-jiuguai-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.238.64/26 | 64 | shanghai-jiushi-renxin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.238.128/27 | 32 | shanghai-suanji-renjiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.238.160/27 | 32 | shanghai-chuli-fasheng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.238.192/26 | 64 | shanghai-tufa-shijian-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.239.0/26 | 64 | shanghai-shigu-qingkuang-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.239.64/26 | 64 | shanghai-chuli-nanshi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.239.128/27 | 32 | shanghai-yingji-chuzhi | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.239.160/27 | 32 | shanghai-wanshan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.239.192/26 | 64 | shanghai-dongqiang-xihu | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.240.0/26 | 64 | shanghai-luoshi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.240.64/26 | 64 | shanghai-anquan-shengchan | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.240.128/27 | 32 | shanghai-guzhang-chuli-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.240.160/27 | 32 | shanghai-shunchang-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.240.192/26 | 64 | shanghai-xunsu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.241.0/25 | 128 | shanghai-tuoshan-xugou-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.241.128/25 | 128 | shanghai-zhixing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.242.0/25 | 128 | shanghai-xingzhi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.242.128/25 | 128 | shanghai-jizhong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.243.0/25 | 128 | shanghai-shengchan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.243.128/25 | 128 | shanghai-jiju-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.244.0/25 | 128 | shanghai-xunluo-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.244.128/25 | 128 | shanghai-xiexie-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.245.0/26 | 64 | shanghai-xuanyang-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.245.64/26 | 64 | shanghai-fangfan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.245.128/25 | 128 | shanghai-shouduan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.246.0/26 | 64 | shanghai-qianjin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.246.64/26 | 64 | shanghai-jiangjun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.246.128/25 | 128 | shanghai-anquanxinxi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.247.0/26 | 64 | shanghai-PE-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.247.64/26 | 64 | shanghai-ceshi-shouli-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.247.128/25 | 128 | shanghai-hangzhou-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.248.0/26 | 64 | shanghai-baozheng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.248.64/26 | 64 | shanghai-hiyi-dianshi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.248.128/25 | 128 | shanghai-jiushi-bahui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.249.0/26 | 64 | shanghai-jiuyue-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.249.64/26 | 64 | shanghai-chujiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.249.128/25 | 128 | shanghai-shiwang-jiuba-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.250.0/26 | 64 | shanghai-wangdongmei-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.250.64/26 | 64 | shanghai-wangdongmei-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.250.128/27 | 32 | shanghai-xiqie-xinjiu-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.250.160/27 | 32 | shanghai-xinyu-jiuhui-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.250.192/26 | 64 | shanghai-lianghao-weichi | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.251.0/26 | 64 | shanghai-cuixin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.251.64/26 | 64 | shanghai-xinghui-xinren-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.251.128/27 | 32 | shanghai-shangjingwen-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.251.160/27 | 32 | shanghai-luoyi-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.251.192/26 | 64 | shanghai-yanfeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.252.0/26 | 64 | shanghai-dingjun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.252.64/26 | 64 | shanghai-chenhao-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.252.128/27 | 32 | shanghai-chenjian-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.252.160/27 | 32 | shanghai-yangbing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.252.192/26 | 64 | shanghai-shenghe-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.253.0/26 | 64 | shanghai-jianlin-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.253.64/26 | 64 | shanghai-wangxiang-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.253.128/27 | 32 | shanghai-wangli-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.253.160/27 | 32 | shanghai-mali-chenhong-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.253.192/26 | 64 | shanghai-menglili-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.254.0/26 | 64 | shanghai-sunxinli-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.254.64/26 | 64 | shanghai-jianfeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.254.128/27 | 32 | shanghai-gaofeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.254.160/27 | 32 | shanghai-wangjing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.254.192/26 | 64 | shanghai-wangjing-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.255.0/26 | 64 | shanghai-yuepeng-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.255.64/26 | 64 | shanghai-qiankun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.255.128/27 | 32 | shanghai-yundian-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.255.160/27 | 32 | shanghai-quanyun-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
| └ 210.22.255.192/26 | 64 | shanghai-wangquan-corp | shanghai city | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-CN |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 10,304 | 63% | 125 | |
| Residential | 2,816 | 17% | 6 | |
| Hosting | 2,048 | 13% | 8 | |
| Internet provider | 1,216 | 7.4% | 4 |
Network & registry
IPv4 market
Holder
- Organization
- China Unicom IP network
- Range
- 210.
21. 0. 0 - 210. 22. 255. 255 - Registration type
- ALLOCATED PORTABLE
Origin network
AS9929
CN
- Name
- CHINA UNICOM Industrial Internet Backbone
- Type
- Internet provider
- Registered
- Apr 5, 2000
- Domain
- chinaunicom.cn
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- May 2005 · 22 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 210.22.192.0/18 | AS9929 | /18 | APNIC | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS9929 | APNIC | cuii | MAINT-CNCGROUP-RR | Aug 24, 2021 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 210.22.194.0/24 | AS9929 | APNIC | cuii | MAINT-CNCGROUP-RR | Aug 24, 2021 |
| 210.22.224.0/20 | AS17621 | APNIC | China Unicom CHINA169 Shanghai Network | MAINT-CNCGROUP-RR | May 4, 2017 |
| 210.22.253.0/24 | AS9929 | APNIC | cuii | MAINT-CNCGROUP-RR | Aug 24, 2021 |
Whois
Registration for this announcement
- Range
- 210.
22. 0. 0/ 16 - Netname
- UNICOM-CN
- Registrant
- China Unicom IP network
- Registrant country
- CN
- Organization
- China Unicom IP network
- Org country
- CN
- Type
- ALLOCATED PORTABLE
- Created
- Not stated by the registry
- Updated
- Oct 21, 2023
- Maintainer
- MAINT-CNCGROUP
- RIR
- APNIC
- Country
- CN
- Delegated
- Oct 17, 2000
- Status
- assigned
Report abuse
Abuse contact
- hqs-ipabuse@
chinaunicom. cn - Name
- ABUSE CUCN
- Handle
- AC1718-AP