Data as of Nov 17, 2026

218.104.80.0/20

No anonymizer space · no proxy exits in 30 days

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

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
74% of it

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.84.0/2732nanjing-yangzi-shihua-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.32/2732nanjing-suocui-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.64/2816nanjing-nanxin-guolv-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.80/2816nanjing-dianzi-jishu-yanjiusuonanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.96/2816nanjing-aoluola-ruanjiannanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.112/2816nanjing-yanjing-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.128/2816nanjing-aideqi-dianxunnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.144/2816nanjing-laoshan-jinggu-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.160/2816nanjing-china-communicationnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.176/2816nanjing-ailixin-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.208/2816nanjing-suning-wuyenanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.240/298nanjing-tongguang-baodiannanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.84.248/298nanjing-fengqing-shizhong-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.85.0/25128nanjing-juyou-network-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.85.128/2664nanjing-shiwuqiang-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.85.192/2732nanjing-fangyuan-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.85.224 - 218.104.85.24017nanjing-guojia-anquan-centernanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.85.240/2816nanjing-youxin-niandu-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.86.0/25128nanjing-banglian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.86.128/25128nanjing-banglian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.87.0/25128nanjing-banglian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.87.128/25128nanjing-banglian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.88.0/25128nanjing-banglian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.88.128/25128nanjing-banglian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.89.0/25128nanjing-fouxin-duri-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.89.128/25128nanjing-andexin-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.90.0/25128nanjing-zhongshan-guangdiannanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.90.128/25128nanjing-zhongshan-guangdiannanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.91.0/2664nanjing-tese-lvxing-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.91.64/2664nanjing-quyu-gejie-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.91.128/25128nanjing-anshan-bushi-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.92.0/2664nanjing-mingpai-tuijin-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.92.64/2664nanjing-qianhai-haibin-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.92.128/25128nanjing-qianhai-haibin-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.93.0/2664nanjing-jingqian-jiuyi-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.93.64/2664nanjing-nanfen-guojiu-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.93.128/25128nanjing-changgui-xianlu-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.94.0/2664nanjing-yuncheyao-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.94.64/2664nanjing-xihan-yuannian-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.94.128/25128nanjing-yuanyong-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.95.0/2664nanjing-ouer-jiuhui-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.95.64/2664nanjing-reai-zuguo-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 218.104.95.128/25128nanjing-gaikuang-corpnanjing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-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

4,096 addresses
TypeAddressesShareRanges
Business3,02474%42
Internet provider1,07226%4

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