LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

210.22.220.0/22

9 residential-proxy exits · 30 days

China Unicom Shanghai network · space held by China Unicom IP network

Announcement
this exact prefix
RPKI valid
Announced by
AS17621
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
9
0.88% of its addresses · 30 days
Always-on exits
1
11% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
33
selling exits here
Oct 13, 2026 – Nov 11, 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

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
210.22.192.0/18
since May 2005
AS9929Internet provider9
1 always on
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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
210.21.0.0 - 210.22.255.255131,072UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 210.22.0.0/1665,536UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 210.22.220.0/2664shanghai-youbang-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.220.64/2664shanghai-youshi-quanti-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.220.128/25128shanghai-qunfeng-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.221.0/2664shanghai-shiyuan-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.221.64/2664shanghai-bingxing-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.221.128/25128shanghai-shuanxing-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.222.0/2664shanghai-shunchang-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.222.64/2664shanghai-tiansu-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.222.128/25128shanghai-woshui-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.223.0/2664shanghai-jingshui-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.223.64/2664shanghai-fangyuan-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.223.128/25128shanghai-qingjing-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
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.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2017
Current origin since
May 2017 · 9.5 yr
Origin networks
1