Data as of Nov 13, 2026

210.22.254.0/23

No anonymizer space · no proxy exits in 30 days

China Unicom Shanghai network · space held by China Unicom IP network

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
210.22.192.0/18
since May 2005
AS9929Internet provider9
1 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
210.21.0.0 - 210.22.255.255131,072UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 210.22.0.0/1665,536UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 210.22.254.0/2664shanghai-sunxinli-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.254.64/2664shanghai-jianfeng-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.254.128/2732shanghai-gaofeng-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.254.160/2732shanghai-wangjing-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.254.192/2664shanghai-wangjing-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.255.0/2664shanghai-yuepeng-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.255.64/2664shanghai-qiankun-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.255.128/2732shanghai-yundian-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.255.160/2732shanghai-quanyun-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.22.255.192/2664shanghai-wangquan-corpshanghai 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.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2020
Current origin since
Oct 2020 · 6.0 yr
Origin networks
1