Data as of Nov 14, 2026

218.6.0.0/17

24 residential-proxy exits · 30 days

China Telecom · space held by Data Communication Division

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
24
0.07% of its addresses · 30 days
Always-on exits
1
4.2% of its exits
Spread
14 of 128
/24s with at least one exit
Providers
46
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

3.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • HELODATA
  • IPCola
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • SpyderProxy
  • TrustProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy

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.0.0.0 - 218.6.255.255458,752CHINANET-CNData Communication DivisionALLOCATED PORTABLE—anti-spam@chinatelecom.cn
└ 218.6.0.0/1732,768CHINANET-FJCHINANET fujian province networkALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-CN
└ 218.6.36.88 - 218.6.36.9710EPB-LY-FJLongyan Electricity Power Bureau FuJian ProvinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.75.80/298TY-XM-FJXiamen TongYong fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.75.112/298WLD-XM-FJXiamen WanLiDa fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.75.120/298TYDQ-XM-FJXiamen TongYongDianQi fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.75.136/298QEMY-XM-FJXiamen QinEnMaoYi fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.75.168/298XY-XM-FJXiamen XunYi fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.75.176/298MH-XM-FJXiamen MinHang fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.76.240/298XDMT-XM-FJXiamen XianDaiMaTou fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.77.24/298ZXZX-XM-FJXiamen ZhongXiaZiXun fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.77.104/298HXWB-XM-FJXiamen HuanXiWangBa fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.77.168/298CYSKWB-XM-FJXiamen ChaoYueShiKongWB fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.77.208/298HA-XM-FJXiamen HengAn fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.77.232/298MLDWB-XM-FJXiamen MeiLianDaWangBa fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.78.48/298XHGX-XM-FJXiamen XingHuiGuangXue fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.78.152/298JMQSNG-XM-FJXiamen JiMeiQinShaoNianGong fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.78.176/298WMDZ-XM-FJXiamen WanMingDianZi fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.79.0/298SHQM-XM-FJXiamen SanHuiQiMao fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.79.40/298XMT-XM-FJXiamen XMTelecom fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.79.72/298CGHB-XM-FJXiamen ChuangGuanHuanBao fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.79.88/298JQWB-XM-FJXiamen JinQiWangBa fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.79.96/298CZMY-XM-FJXiamen CaiZhiMaoYi fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn
└ 218.6.79.200/298GJJJ-XM-FJXiamen GuoJiJingJi fujian provinceASSIGNED NON-PORTABLE—fjnic@fjdcb.fz.fj.cn

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

32,768 addresses
TypeAddressesShareRanges
Residential32,590>99%20
Business1780.54%22

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1