Data as of Nov 16, 2026

210.51.236.0/24

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
210.51.192.0/18
since May 2005
AS9929Internet providerChina Unicom IP network
210.51.0.0/16
since May 2005
AS9929Internet provider61
3 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.51.0.0/1665,536UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 210.51.236.0/2816WUHAN-XINPENGwuhan cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.16 - 210.51.236.4732shanghai-fushou-corpshanghai cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.48/2816HUBEI-JUYOUwuhan cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.64/2664WUHAN-SHIMAO-MANSIONwuhan cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.128/2664XINCHANG-GUANGDIANbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.192/2816ZHAOYIN-MANSIONzhaoyin mansion,wuhan city,hubei provinceASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.208/2816CHANGLE-UPTOWNWuhan Changle uptownASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.224/2816PANDA-GROUP-EMPLOYEE-UPTOWNNanjing Panda Group EmployeeASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.51.236.240/2816HUANGPU-GARDENNanjing Huangpu garden,HuangpuASSIGNED 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
Jul 2024
Current origin since
Jul 2024 · 2.4 yr
Origin networks
1