Data as of Nov 10, 2026

116.115.48.0/22

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

Exits seen per day

70 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLEETPROXY
  • GSocks
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SPYDERPROXY_PREMIUM
  • Shifter
  • 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.48.0/24256IMWEIP1Inner Mongolia Jining ERX1400 IP POOL1ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via InnerMongoliaJiningZXSB14MH01erx1
└ 116.115.49.0/24256IMWEIP2Inner Mongolia Jining ERX1400 IP POOL2ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via InnerMongoliaJiningZXSB14MH01erx1
└ 116.115.50.0/24256IMWEIP3Inner Mongolia Jining ERX1400 IP POOL3ASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via InnerMongoliaJiningZXSB14MH01erx1
└ 116.115.51.0/24256IMWEIP4Inner Mongolia Jining ERX1400 IP POOL4ASSIGNED 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