Data as of Nov 12, 2026

210.82.98.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

AS4808

Type

Residential

98% of it

Announcements

Less specific

Covering announcements

Prefix	Origin	Type	Proxy exits	Holder	RPKI
210.82.0.0/17 since Sep 2010	AS4808	Residential	4	China 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.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
210.82.0.0/15	131,072	UNICOM-CN	China Unicom IP network	ALLOCATED PORTABLE	—	hqs-ipabuse@chinaunicom.cn
└ 210.82.0.0/17	32,768	UNICOM-BJ	China Unicom Beijing province network	ALLOCATED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-CN
└ 210.82.98.4/30	4	YASHANG-LIANMENG-LTD	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.8/30	4	beijing-jingguang-linjiang-zhiye	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.12/30	4	beijing-zhaoshang-yinghang	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.16/30	4	beijing-xiandai-decheng-gongmao	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.20/30	4	beijing-oubeite-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.24/30	4	beijing-quanjing-network	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.28/30	4	beijing-jinxiao-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.32/29	8	beijing-zhongcai-weiyuan	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.40/29	8	beijing-huicong-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.48/28	16	beijing-yuanyang-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.64/29	8	beijing-zhaoshangju	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.128/29	8	beijing-baoyuan-gongmao	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.136/29	8	beijing-wangjing-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.144/29	8	beijing-jiaohui-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.152/29	8	beijing-jiaowei-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.160/27	32	beijing-conghui-corp	beijing city	ASSIGNED NON-PORTABLE	—	hqs-ipabuse@chinaunicom.cn via UNICOM-BJ
└ 210.82.98.192/26	64	beijing-kuaireng-corp	beijing city	ASSIGNED 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

Type	Addresses	Share	Ranges
Residential	252	98%	2
Business	4	1.6%	1

Network & registry

Announcement Routing history RPKI & IRR Whois & abuse

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern: Stable
First seen: Aug 2017
Current origin since: Aug 2017 · 9.2 yr
Origin networks: 1

ROA prefix	ASN	Max len	Anchor	Verdict
210.82.98.0/24	AS4808	/24	APNIC	RPKI valid
210.82.0.0/17	AS4808	/17	APNIC	Too specific