Data as of Nov 16, 2026

125.35.5.0/24

1 residential-proxy exit · 30 days

China Unicom Beijing Province Network

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
19
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

127 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • HydraProxy
  • Infatica
  • MangoProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalData

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
125.35.0.0/18
since Sep 2010
AS4808Residential10China Unicom Beijing province network
125.35.0.0/17
since Feb 2006
AS4808Residential31China Unicom Beijing province network

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
125.35.0.0/1732,768UNICOM-BJChina Unicom Beijing province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 125.35.0.0/198,192CHINAUNICOMChina Unicom Beijing province networkALLOCATED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 125.35.5.0/24256UFIDA-COunknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via CHINAUNICOM

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

125.35.0.0/19

Routing history

Pattern
Stable
First seen
Jul 2018
Current origin since
Jul 2018 · 8.3 yr
Origin networks
1