Data as of Nov 12, 2026

115.46.0.0/16

392 residential-proxy exits · 30 days

CHINA UNICOM China169 Backbone · space held by China Unicom Guangxi province network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
392
0.60% of its addresses · 30 days
Spread
84 of 256
/24s with at least one exit
Providers
43
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

18K observations

Proxy providers listing exits

  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPCola
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
115.46.32.0/24
since Jan 2026
AS9929ResidentialChina Unicom Guangxi 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
115.46.0.0/1665,536UNICOM-GXChina Unicom Guangxi province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 115.46.32.0 - 115.46.44.2553,328GL-PPPOE-2008GL-pppoe-2008ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GX
└ 115.46.160.0/24256CNCFCG-DXADSL6CNC-FCG-INTER-dongxing-pppoe,FangChengGang,GuangXi,CHINAASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GX
└ 115.46.161.0/24256CNCFCG-DXADSL7CNC-FCG-INTER-dongxing-pppoe,FangChengGang,GuangXi,CHINAASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GX

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jul 2008
Current origin since
Jul 2008 · 18 yr
Origin networks
1