No.31, Jin-rong Street

NANPING-TELECOM-BUREAU

BGP inherited

Cluster stats

Netblocks	2
All fragments	9 blocks across 6 clusters
Cluster ID	206398156
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

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

IP Ranges (2)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
202.109.229.8/29	NANPING-TELECOM-BUREAU	APNIC	ASSIGNED NON-PORTABLE	● low
202.109.230.104/29	NANPING-TELECOM-BUREAU	APNIC	ASSIGNED NON-PORTABLE	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “NANPING 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.

NANPING-TELECOM-NANPING-FJ 3 blocks
NANPING-TELECOM-COM 1 blocks
NANPING-TELECOM-CHARGE 1 blocks
NANPING-TELECOM-JIANYAN-TO-NANPING-FJ 1 blocks
NANPING-TELECOM-SHUNCHANG-TO-NANPING-FJ 1 blocks

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.

NANPING-TELECOM-COM via No.31,Jin-rong Street sub-allocation
NANPING-WUYISHAN-TELECOM via No.31,Jin-rong Street sub-allocation
NANPING-TELECOM-CHARGE via No.31,Jin-rong Street sub-allocation
NANPING-TELECOM-JIANYAN-TO-NANPING-FJ via No.31,Jin-rong Street sub-allocation
NANPING-TELECOM-SHUNCHANG-TO-NANPING-FJ via No.31,Jin-rong Street sub-allocation
NANPING-WUYI-TELECOM via No.31,Jin-rong Street sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

LG52-AP LG52-AP MAINT-CHINANET-FJ MD47-AP MD47-AP