Data as of Nov 13, 2026

110.18.44.0/22

7 residential-proxy exits · 30 days

UNICOM InnerMongolia province network · space held by China Unicom InnerMongolia province network

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

Residential-proxy exits

Proxy exits
7
0.68% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
110.18.47.0/2406
110.18.46.0/2401

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GonzoProxy
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
110.16.0.0/14
since Apr 2009
AS4837Residential995
13 always on
China Unicom InnerMongolia 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
110.16.0.0/14262,144UNICOM-NMChina Unicom InnerMongolia province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 110.18.32.0/204,096InnerMongoliaJiningXQAB80MH01pool2unknownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-NM

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