Data as of Nov 18, 2026

61.50.192.0/18

2 residential-proxy exits · 30 days

China Unicom Beijing Province Network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
2
0.01% of its addresses · 30 days
Spread
2 of 64
/24s with at least one exit
Providers
24
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

143 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
61.50.196.0/2401
61.50.213.0/2401

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
61.50.128.0/17
since Aug 2007
AS4808Residential24
1 always on
China Unicom Beijing province network
via China Netcom Group Beijing Corporation
61.50.0.0/16
since Jul 2006
AS4808Residential47
3 always on
China Unicom Beijing province network
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
61.50.244.0/24
since Aug 2026
AS4837ResidentialChina Unicom Beijing province network
via China Netcom Group Beijing Corporation
61.50.246.0/24
since Aug 2026
AS4837ResidentialChina Unicom Beijing province network
via China Netcom Group Beijing Corporation

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
61.48.0.0/14262,144UNICOM-BJChina Unicom Beijing province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 61.50.128.0/1732,768CNCBTJQ-NETChina Netcom Group Beijing CorporationALLOCATED 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
Aug 2007 · 19 yr
Origin networks
2
Last change of origin
Aug 2007
Recorded history

History

Handoffs
1