Data as of Nov 21, 2026

218.106.82.0/24

10 residential-proxy exits · 30 days

UNICOM AnHui province network · space held by China Unicom IP network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Providers
28
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

651 observations

Proxy providers listing exits

  • AETHYN_BASIC
  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • DataImpulse
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPRoyal
  • Infatica
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NodeProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyRack
  • Proxyma
  • SOTAPROXY
  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
218.106.80.0/20
since Aug 2006
AS4837Residential15China Unicom IP network
via Anhui Hefei branch of China Netcom
218.106.0.0/17
since May 2005
AS9929Internet provider68
8 always on
China Unicom IP 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
218.104.0.0/14262,144UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.106.80.0/204,096CNC-AH-hefei-MANAnhui Hefei branch of China NetcomALLOCATED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.106.82.64/2664Hefei-CATV-netcomHefei-CATV-netcom AnHuiASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via CNC-AH-hefei-MAN
└ 218.106.82.128/2664hefei-jinma-lvxingshehefei cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via CNC-AH-hefei-MAN
└ 218.106.82.192/2664hefei-congwenmen-corphefei cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via CNC-AH-hefei-MAN

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
Dec 2020
Current origin since
Dec 2020 · 6.0 yr
Origin networks
1