BEIJING-CN

BGP inherited

Cluster stats

Netblocks	7 · 755 IPv4 addresses
Cluster ID	212406269
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 15 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

7 0 netblocks since 2026-07-05

2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
203.93.218.0/29	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high
203.93.218.16 – 203.93.218.80	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high
203.93.218.81 – 203.93.218.209	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high
203.93.247.0/24	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high
210.12.0.80/28	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high
210.12.0.96/27	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high
210.12.190.0/24	BEIJING-CN	APNIC	ASSIGNED NON-PORTABLE	● high

Possibly related to this organisation

what's this?

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

JTBEIJING-CN via China Unicom sub-allocation
Beijing CN Link Network Technology Co Ltd Guangzhou Branch Age sub-allocation
beijing-cnc-jiaohui-corp via China Unicom sub-allocation

Network trust

what's this?

RPKI hygiene: B how networks compare →

85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)

Possible discrepancies (1)

These blocks are registered to BEIJING-CN but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

210.12.190.0/24 /24

authorized for AS4808 — China Unicom

NIC Handles

DW65-AP DW65-AP HL221-AP HL221-AP JS108-AP JS108-AP LZ75-AP LZ75-AP MAINT-CHINAGBN-AP NZ6-AP NZ6-AP SH124-AP +3 more