Data as of Nov 21, 2026

202.106.48.0/20

6 residential-proxy exits · 30 days

China Unicom Beijing Province Network

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

Residential-proxy exits

Proxy exits
6
0.15% of its addresses · 30 days
Always-on exits
4
67% of its exits
Spread
2 of 16
/24s with at least one exit
Providers
36
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

7.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
202.106.50.0/2445
202.106.54.0/2401

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
202.106.0.0/18
since Jul 2006
AS4808Residential8
4 always on
China Unicom Beijing province network
202.106.0.0/16
since Jul 2006
AS4808Residential40
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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
202.106.0.0/1665,536UNICOM-BJChina Unicom Beijing province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 202.106.58.0/24256IPPH-COIntellectual Property Publishing HouseASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1