Data as of Nov 14, 2026

218.104.71.0/24

9 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
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
44
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.5K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PSBProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • Shifter
  • VProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
218.104.64.0/20
since Aug 2006
AS4837Residential18
2 always on
China Unicom IP network
via Anhui Hefei branch of China Netcom

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.104.64.0/204,096CNC-AH-hefei-MANAnhui Hefei branch of China NetcomALLOCATED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.71.0/25128hefei-aipu-techhefei cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via CNC-AH-hefei-MAN
└ 218.104.71.128/25128hefei-tech-touzi-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 · 5.9 yr
Origin networks
1