Data as of Nov 16, 2026

27.38.243.0/24

16 residential-proxy exits · 30 days

China Unicom Shenzen network · space held by China Unicom Guangdong province network

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

Residential-proxy exits

Proxy exits
16
6.3% of its addresses · 30 days
Providers
40
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.2K observations

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • HASDATA
  • HELODATA
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • QUANTICDATA
  • RainProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
27.38.0.0/16
since Nov 2010
AS17623Residential4,479China Unicom Guangdong province network
via China Unicom Shenzhen city network
27.36.0.0/14
since Mar 2010
AS17816Residential6,669
1 always on
China Unicom Guangdong 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
27.36.0.0/14262,144UNICOM-GDChina Unicom Guangdong province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 27.38.0.0/1665,536UNICOM-GDSZChina Unicom Shenzhen city networkALLOCATED 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
Jan 2024
Current origin since
Jan 2024 · 2.8 yr
Origin networks
1