Data as of Nov 16, 2026

218.29.99.0/24

12 residential-proxy exits · 30 days

CHINA UNICOM China169 Backbone · space held by China Unicom Henan province network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Providers
26
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

271 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
218.28.0.0/15
since May 2005
AS4837Residential471
35 always on
China Unicom Henan 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
218.28.0.0/15131,072UNICOM-HAChina Unicom Henan province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.0/2732HA-ZZ-ZYZQGFYXGS-LTDZYZQGFYXGS LtdASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.32/298HA-ZZ-TJTSSWGCYXGSF-CORPTJTSSWGCYXGSF CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.40/298HA-ZZ-CGNFCPJGC-CORPCGNFCPJGC CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.48/298HA-ZZ-YXKJFZSZYXGS-CORPYXKJFZSZYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.56/298HA-ZZ-SFCWXXZXYXGS-CORPSFCWXXZXYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.64/298HA-ZZ-KLLJJDGLYXGS-CORPKLLJJDGLYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.72/298HA-ZZ-ZYQXXZX-CENTERZYQXXZX CenterASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.80/2816HA-ZZ-JYWLXXFWYXGS-CORPJYWLXXFWYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.96/298HA-ZZ-ZYQXXZX-CENTERZYQXXZX CenterASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.104/298HA-ZZ-GLZYYXGS-CORPGLZYYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.112/298HA-ZZ-DERMYY-HOSPITALDERMYY HospitalASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.120/298HA-ZZ-MLMJMXYJS-CORPMLMJMXYJS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.128/298HA-ZZ-YFTZXZXYXGS-CORPYFTZXZXYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.136/298HA-ZZ-XQDYWYXGS-CORPXQDYWYXGS CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA
└ 218.29.99.144/298HA-ZZ-YongLeHaoCai-CORPYongLeHaoCai CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.152/304HA-ZZ-WuLongKou-CORPWuLongKou CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.156/304HA-ZZ-XinYaFuZhuang-CORPXinYaFuZhuang CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.160/298HA-ZZ-JingWeiGuanZh-CORPJingWeiGuanZhuang CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.168/298HA-ZZ-ZhongYuan-NETBARZhongYuan NetBarASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.176/298HA-ZZ-RenDa-CORPRenDa CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.184/298HA-ZZ-XinDongTiYu-CORPXinDongTiYu CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.192/2816HA-ZZ-GuanWeiHui-CORPGuanWeiHui CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.208/2816HA-ZZ-LanDun-CORPLanDun CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.29.99.224/2732HA-ZZ-YZXXJ-CORPYZXXJ CorpASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-HA

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 2025
Current origin since
Dec 2025 · 11 mo
Origin networks
1