Data as of Nov 22, 2026

218.104.200.0/21

1 residential-proxy exit · 30 days

CHINA UNICOM Industrial Internet Backbone · space held by China Unicom IP network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
53% of it

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
4
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

4 observations

Proxy providers listing exits

  • Byteful
  • GSocks
  • Infatica
  • PROXYSCRAPE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
218.104.128.0/17
since May 2005
AS9929Internet provider85
4 always on
China 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.104.200.0/212,048UNICOM-SCChina Unicom SiChuan province networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 218.104.204.0/25128chengdu-guangshang-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.204.128/25128chengdu-raoxing-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.205.0/25128chengdu-shunjiu-tianyi-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.205.128/25128chengdu-nanguo-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.206.0/25128chengdu-feixu-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.206.128/25128chengdu-yangxingping-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.0/298JIABIN-DIANZIchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.8/298CNC-XIYUANchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.16/298ZONGFU-HOTELchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.24/298CHENGDU-FANGDICHANchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.32/304XINJIAPO-GARDENchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.36/304XUEFU-GARDENchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.40/304FANGCAODI-XIAOQUchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.44/304sichuan-dianli-shejichengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.48/2816sichuan-ertan-xinxingchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.64/298sichuan-shenghe-zhiyaochengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.72/298chengdu-yangxingping-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.80/298sichuan-yingli-shuju-Ltdchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.88/298chengdu-yinyongshui-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.96/2816chengdu-guanzhi-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.112/2816chengdu-suoyiran-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.192/2816SICHUAN-TAILONG-TONGXIN-CORPchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.208/2816chengdu-yiguo-qinglv-corpchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC
└ 218.104.207.224/2732SHANGHAI-FEISITE-CORPchengdu cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-SC

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

2,048 addresses
TypeAddressesShareRanges
Internet provider1,08853%2
Business96047%24

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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