Data as of Nov 5, 2026
222.128.0.0/14
No anonymizer spaceChina Unicom Beijing Province Network
Residential-proxy exits
Proxy exits
823
0.31% of its addresses · listed by providers
Always-on exits
31
3.8% of its exits
Spread
295 of 1,024
/24s with at least one exit
Providers
82
selling exits here
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- BartProxies
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- ColaProxy
- CoreProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- PSBProxy
- PacketStream
- PrivateByte
- Proxies.fo
- ProxiesVision
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- ResiProxies
- Shifter
- SpyderProxy
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- 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 |
|---|---|---|---|---|---|
| 222.128.0.0/16 since Jul 2006 | AS4808 | Residential | 226 10 always on | China Unicom Beijing province network | |
| 222.128.0.0/18 since Aug 2007 | AS4808 | Residential | 87 2 always on | China Unicom Beijing province network | |
| 222.128.64.0/18 since Aug 2007 | AS4808 | Residential | 44 4 always on | China Unicom Beijing province network | |
| 222.128.128.0/18 since Aug 2007 | AS4808 | Residential | 84 4 always on | China Unicom Beijing province network | |
| 222.128.192.0/18 since Aug 2007 | AS4808 | Residential | 11 | China Unicom Beijing province network | |
| 222.128.192.0/20 since Jul 2006 | AS4808 | Residential | 10 | China Unicom Beijing province network | |
| 222.128.192.0/21 since Jul 2006 | AS4808 | Residential | 3 | China Unicom Beijing province network | |
| 222.128.200.0/21 since Jul 2006 | AS4808 | Residential | 7 | China Unicom Beijing province network | |
| 222.128.208.0/20 since Feb 2008 | AS4808 | Residential | China Unicom Beijing province network | ||
| 222.128.208.0/21 since Feb 2008 | AS4808 | Residential | China Unicom Beijing province network | ||
| 222.128.216.0/21 since Feb 2008 | AS4808 | Residential | China Unicom Beijing province network | ||
| 222.128.247.0/24 since Aug 2007 | AS4808 | Residential | China Unicom Beijing province network | ||
| 222.129.0.0/16 since Jul 2006 | AS4808 | Residential | 268 9 always on | China Unicom Beijing province network | |
| 222.129.0.0/18 since Aug 2007 | AS4808 | Residential | 44 4 always on | China Unicom Beijing province network | |
| 222.129.64.0/18 since Aug 2007 | AS4808 | Residential | 24 | China Unicom Beijing province network | |
| 222.129.128.0/18 since Aug 2007 | AS4808 | Residential | 103 3 always on | China Unicom Beijing province network | |
| 222.129.152.0/21 since Jan 2021 | AS4808 | Residential | China Unicom Beijing province network | ||
| 222.129.192.0/18 since Aug 2007 | AS4808 | Residential | 97 2 always on | China Unicom Beijing province network | |
| 222.129.240.0/21 since Nov 2007 | AS4808 | Residential | 75 2 always on | China Unicom Beijing province network | |
| 222.130.0.0/16 since Jul 2006 | AS4808 | Residential | 59 4 always on | China Unicom Beijing province network | |
| 222.130.0.0/18 since Aug 2007 | AS4808 | Residential | 8 | China Unicom Beijing province network | |
| 222.130.16.0/20 since May 2017 | AS4808 | Residential | 4 | China Unicom Beijing province network | |
| 222.130.64.0/18 since Aug 2007 | AS4808 | Residential | 7 1 always on | China Unicom Beijing province network | |
| 222.130.128.0/18 since Aug 2007 | AS4808 | Residential | 22 | China Unicom Beijing province network | |
| 222.130.192.0/18 since Aug 2007 | AS4808 | Residential | 22 3 always on | China Unicom Beijing province network | |
| 222.131.0.0/16 since Jul 2006 | AS4808 | Residential | 270 8 always on | China Unicom Beijing province network | |
| 222.131.0.0/18 since Aug 2007 | AS4808 | Residential | 87 1 always on | China Unicom Beijing province network | |
| 222.131.64.0/18 since Aug 2007 | AS4808 | Residential | 45 1 always on | China Unicom Beijing province network | |
| 222.131.128.0/18 since Aug 2007 | AS4808 | Residential | 33 2 always on | China Unicom Beijing province network | |
| 222.131.192.0/18 since Aug 2007 | AS4808 | Residential | 105 4 always on | China Unicom Beijing province 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 |
|---|---|---|---|---|---|---|
| 222.128.0.0/14 | 262,144 | UNICOM-BJ | China Unicom Beijing province network | ALLOCATED PORTABLE | — | hqs-ipabuse@ |
| └ 222.128.193.128/28 | 16 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.193.144/28 | 16 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.193.160/28 | 16 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.193.176/28 | 16 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.193.192/28 | 16 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.193.208/28 | 16 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.193.224/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.16/28 | 16 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.32/28 | 16 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.48/28 | 16 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.64/28 | 16 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.80/28 | 16 | OC-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.96/28 | 16 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.112/28 | 16 | ABC-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.197.128/25 | 128 | WSHM-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.0/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.32/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.64/27 | 32 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.96/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.128/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.160/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.192/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.201.224/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.202.0/24 | 256 | SLHB-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.0/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.32/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.64/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.96/27 | 32 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.128/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.160/27 | 32 | CNC | CNC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.203.224/27 | 32 | OLYMPIC-BROADCAST-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.205.0/25 | 128 | OC-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.205.128/27 | 32 | BH | BH | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.205.192/26 | 64 | OC-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.206.0/24 | 256 | OC-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.207.0/24 | 256 | OC-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.208.0/24 | 256 | BIMC | BIMC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.209.0/25 | 128 | AT | AT | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.209.128/26 | 64 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.209.192/26 | 64 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.210.0/24 | 256 | BIMC | BIMC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.211.0/24 | 256 | BIMC | BIMC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.212.0/24 | 256 | BIMC | BIMC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.213.0/24 | 256 | BTV | BTV | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.214.0/24 | 256 | BTV | BTV | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.215.0/26 | 64 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.215.64/26 | 64 | AYZJ | AYZJ | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.215.128/25 | 128 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.0/25 | 128 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.128/29 | 8 | MGZTFH | MGZTFH | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.136/29 | 8 | AYZJ | AYZJ | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.144/29 | 8 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.152/29 | 8 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.160/27 | 32 | AOC | AOC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.192/27 | 32 | AOC | AOC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.216.224/28 | 16 | OLYMPIC-BROADCAST-CO | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.217.0/24 | 256 | BIMC | BIMC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.218.0/23 | 512 | BTV | BTV | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.220.0/24 | 256 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.221.0/24 | 256 | BOCOG-ORG | unknown | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
| └ 222.128.222.0/24 | 256 | BIMC | BIMC | ASSIGNED NON-PORTABLE | — | hqs-ipabuse@ via UNICOM-BJ |
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
262,144 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 260,320 | >99% | 36 | |
| Business | 1,824 | 0.70% | 47 |
Network & registry
Origin network
AS4808
CN
- Name
- China Unicom Beijing Province Network
- Type
- Internet provider
- Registered
- Jan 9, 1996
- 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 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 222.128.0.0/14 | AS4808 | /14 | APNIC | RPKI valid |
Whois
Registration for this announcement
- Range
- 222.
128. 0. 0/ 14 - Netname
- UNICOM-BJ
- Registrant
- China Unicom Beijing province network
- Registrant country
- CN
- Organization
- China Unicom Beijing province network
- Org country
- CN
- Type
- ALLOCATED PORTABLE
- Created
- Not stated by the registry
- Updated
- Jan 22, 2025
- Maintainer
- APNIC-HM
- RIR
- APNIC
- Country
- CN
- Delegated
- Nov 19, 2003
- Status
- assigned
Report abuse
Abuse contact
- hqs-ipabuse@
chinaunicom. cn - Name
- ABUSE CUCN
- Handle
- AC1718-AP