K Telecom Ldt.
Cluster stats
Netblocks16
All fragments 116 blocks across 7 clusters
Cluster ID191838888
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

Footprint over time

2 weekly snapshots · JSON
16 0 netblocks since 2026-07-05
2026-07-05 peak 16 2026-07-06

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
178.18.225.13/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
178.18.225.238/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
178.18.233.24/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
185.0.13.138/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
185.1.153.196/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
194.85.107.34/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
194.226.100.234/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
194.226.102.234/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
195.208.210.234/32 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2001:7f8:20:101::210:234/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2001:7f8:20:201::100:234/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2001:7f8:20:202::102:234/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2001:7f8:20:301::107:34/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2a03:5f80:4::225:13/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2a03:5f80:4::225:238/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high
2a03:5f80:4:1::233:24/128 K Telecom Ldt. PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
62.5% of checked blocks have valid RPKI ROA coverage (10 of 16)
No discrepancies found among checked blocks.

NIC Handles

AS48642