Data as of Nov 13, 2026

210.82.56.0/24

No anonymizer space · no proxy exits in 30 days

China Unicom Beijing Province Network · reallocated from China Unicom IP network

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

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
210.82.0.0/17
since Sep 2010
AS4808Residential4China Unicom IP network
via China Unicom Beijing province 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.82.0.0/15131,072UNICOM-CNChina Unicom IP networkALLOCATED PORTABLE—hqs-ipabuse@chinaunicom.cn
└ 210.82.0.0/1732,768UNICOM-BJChina Unicom Beijing province networkALLOCATED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-CN
└ 210.82.56.16/2816ELECTRIC-TOWN-TECH-GARDENbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.32/2732BJ-JINGFDONGFANG-TECH-CORPbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.64/304BJ-JINGFDONGFANG-TECH-CORPbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.68/304beijing-jiaohui-corpbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.72/304beijing-yuefen-luofen-corpbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.76/304beijing-fangyuan-jiuhui-corpbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.80/2816beijing-shihui-pingguo-corpbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.96/2732beijing-huizhan-jiuguai-corpbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ
└ 210.82.56.128/25128beijing-jiujiu-guiyi-corpbeijing cityASSIGNED NON-PORTABLE—hqs-ipabuse@chinaunicom.cn
via UNICOM-BJ

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

256 addresses
TypeAddressesShareRanges
Residential20480%2
Business5220%3

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2018
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1