Data as of Nov 14, 2026

61.49.64.0/18

61 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
61
0.37% of its addresses · 30 days
Spread
20 of 64
/24s with at least one exit
Providers
42
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
61.49.0.0/16
since Aug 2007
AS4808Residential122
1 always on
China Unicom Beijing province network
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
61.49.86.0/24
since May 2008
AS4837ResidentialChina 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.49.86.0/24256ICCInternational Communication CenterASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 61.49.87.0 - 61.49.88.255512YANSHANSHIYOU-COunknownASSIGNED 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