KIEN

BGP inherited

Cluster stats

Netblocks	6
All fragments	9 blocks across 3 clusters
Cluster ID	210090661
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

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

Footprint over time

5 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
195.85.172.240/29	KIEN	RIPE	ASSIGNED PA	● low
213.34.0.0/30	KIEN	RIPE	ASSIGNED PA	● low
213.126.9.32/29	KIEN_BV	RIPE	ASSIGNED PA	● low
2001:41f0:281a::/48	KIEN	RIPE	ASSIGNED	● low
2001:41f0:63d9::/48	KIEN_BV	RIPE	ASSIGNED	● low
2001:41f0:975b::/48	KIEN	RIPE	ASSIGNED	● low

Possibly related to this organisation

what's this?

Same name family

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

KIEN-1637762-Nagpur 2 blocks
KIEN-HWY-AT 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.

Kien Hung sub-allocation
Hands Skien via GLOBALCONNECT AS sub-allocation
Kiendler-GmbH via T-Mobile Austria GmbH sub-allocation
KIENZERL-LAN sub-allocation
MPWIKMIEJSKIENET-PL via Netia SA sub-allocation
Architekt_Kiener via Hutchison Drei Austria GmbH sub-allocation
Mag-Dieter-Kienberger via T-Mobile Austria GmbH sub-allocation
VDOKIENZ01 sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ZIGGO-AUTOREG1