Data as of Nov 17, 2026

218.107.0.0/19

52 residential-proxy exits · 30 days

China Unicom Guangzhou network · space held by China Unicom IP network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
52
0.63% of its addresses · 30 days
Always-on exits
3
5.8% of its exits
Spread
11 of 32
/24s with at least one exit
Providers
48
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

5.7K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • HELODATA
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
218.107.0.0/18
since May 2005
AS17622Residential122
4 always on
China Unicom IP network
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
218.107.0.0/20
since Aug 2009
AS17622Residential25
1 always on
China Unicom IP network
218.107.1.0/24
since Dec 2025
AS17622Residential1China Unicom IP network
218.107.5.0/24
since Aug 2025
AS17622Residential1China Unicom IP network
218.107.16.0/21
since Sep 2016
AS17622Residential27
2 always on
China Unicom IP network
218.107.28.0/22
since Jun 2008
AS17622ResidentialChina 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.107.0.0/1816,384UNICOM-GDChina Unicom Guangdong province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.107.0.0/212,048JUNIPER1-PPPOE-CPN-POOLguangzhou cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD
└ 218.107.19.0/24256LEASED-LINE-THINKER--VOIPguangzhou cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD
└ 218.107.20.0/221,024JUNIPER2-PPPOE-BUILDING-POOLguangzhou cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD
└ 218.107.24.0/221,024TY-ERX710-PPPOE-CUSTOMER-POOLguangzhou cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD
└ 218.107.28.0/221,024TH-ERX710-PPPOE-POOLguangzhou cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-GD

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
Apr 2016
Current origin since
Apr 2016 · 11 yr
Origin networks
1