No.31, Jin-rong Street

TAIZHOU-TELECOM-GLOBALEYE

BGP inherited

Cluster stats

Netblocks	1
All fragments	165 blocks across 54 clusters
Cluster ID	206598005
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

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

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
222.190.155.96/30	TAIZHOU-TELECOM-GLOBALEYE	APNIC	ASSIGNED NON-PORTABLE	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “TAIZHOU TELECOM” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

TAIZHOU-TELECOM-PATX-GLOBALEYE 47 blocks
TAIZHOU-TELECOM 32 blocks
TAIZHOU-TELECOM-TXPSB-GLOBALEYE 10 blocks
TAIZHOU-TELECOM-PSB-GLOBALEYE 10 blocks
TAIZHOU-TELECOM-GQDL-GLOBALEYE 4 blocks
TAIZHOU-TELECOM-CENTER 3 blocks
TAIZHOU-TELECOM-CLIENT-DEP 3 blocks
TAIZHOU-TELECOM-OPERATING-OFFICE 3 blocks

Combined view of all 54 name-family clusters →

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.

TAIZHOU-JJ-TELECOM-YYZX sub-allocation
TAIZHOU-JJ-TELECOM-CHENGNAN sub-allocation
TAIZHOU-TELECOM-MUXIAO-OFFICE via No.31,Jin-rong Street sub-allocation
TAIZHOU-TELECOM-FCHX-DEPT sub-allocation
TAIZHOU-TELECOM-XQCSJF-GLOBALEYE sub-allocation
TAIZHOU-TELECOM-XBK-GLOBALEYE sub-allocation
TAIZHOU-TELECOM-HG-GLOBALEYE sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

CH452-AP CH452-AP MAINT-CHINANET-JS