Data as of Nov 19, 2026

61.50.128.0/22

1 residential-proxy exit · 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
1
0.10% of its addresses · 30 days
Always-on exits
1
100% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
19
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

4.7K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • LightningProxies
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Shifter
  • VibeProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
61.50.128.0/18
since Aug 2007
AS4808Residential22
1 always on
China Unicom Beijing province network
via China Netcom Group Beijing Corporation
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

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
Apr 2008
Current origin since
Apr 2008 · 19 yr
Origin networks
1