Kuzey DC

KuzeyDC
Data as of 2026-09-13
Registry
This organisation
Netblocks7
IPv6 6 prefixes (largest 2001:7f8:11d::22/128)
Record ID242369447
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.221.22/32 KuzeyDC PEERINGDB ASSIGNED ● high
2001:7f8:11d::22/128 KuzeyDC PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:3::13b/128 KuzeyDC PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:10::19c/128 KuzeyDC PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::170/128 KuzeyDC PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:25::181/128 KuzeyDC PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:46::17f/128 KuzeyDC PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Footprint over time

5 weekly snapshots · JSON
7 +1 netblocks since 2026-08-16
2026-08-16 peak 7 2026-09-13

Network trust

what's this?
RPKI hygiene: F how networks compare →
14.3% of checked blocks have valid RPKI ROA coverage (1 of 7)
No discrepancies found among checked blocks.

NIC Handles

AS62425