Data as of Nov 14, 2026

124.67.104.0/22

13 residential-proxy exits · 30 days

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

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

Residential-proxy exits

Proxy exits
13
1.3% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
28
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
124.67.104.0/24011
124.67.106.0/2402

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • VibeProxies
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
124.67.0.0/16
since Aug 2006
AS4837Residential129
3 always on
China Unicom Neimeng Province Network

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
124.67.0.0/1665,536UNICOM-NMChina Unicom Neimeng Province NetworkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 124.67.104.0/221,024InnerMongoliaJiningZXHB52MH01vlan3unknownASSIGNED 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

124.67.96.0/20

Routing history

Pattern
Stable
First seen
May 2019
Current origin since
May 2019 · 7.5 yr
Origin networks
1