Data as of Nov 10, 2026

116.115.63.0/24

30 residential-proxy exits · 30 days

UNICOM InnerMongolia province network · space held by China Unicom Neimeng Province Network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
30
12% of its addresses · 30 days
Providers
41
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • GSocks
  • Geonode
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • PrivateByte
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • RealProxy
  • ResiProxies
  • Shifter
  • TrueProxies
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
116.112.0.0/14
since Jun 2007
AS4837Residential1,125
12 always on
China Unicom Neimeng 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
116.112.0.0/14262,144UNICOM-NMChina Unicom Neimeng Province NetworkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 116.115.48.0/204,096InnerMongoliaJiningZXSB14MH01erx1unknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM
└ 116.115.63.0/24256IMWEIP16Inner Mongolia Jining ERX1400 IP POOL16ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via InnerMongoliaJiningZXSB14MH01erx1

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 2019
Current origin since
May 2019 · 7.5 yr
Origin networks
1