KTV TELECOM
Cluster stats
| Netblocks | 20 |
| All fragments | 100 blocks across 16 clusters |
| Cluster ID | 192263429 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
20
0 netblocks since 2026-07-05
2026-07-05
peak 20
2026-07-06
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.44.186.9/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 31.44.186.10/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 146.185.252.128/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 146.185.252.162/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 178.18.224.128/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 178.18.225.219/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.0.13.170/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.0.13.213/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.152.119/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 185.1.152.196/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 193.27.37.87/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 193.27.37.122/32 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::224:128/128 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::225:219/128 | KTV TELECOM | PEERINGDB | ASSIGNED | ● high |
| 87.48.158.80/28 | KTV-TV-WAN | RIPE | ASSIGNED PA | ● low |
| 87.54.4.0/28 | KTV-TV-WAN | RIPE | ASSIGNED PA | ● low |
| 87.54.4.16/29 | KTV-TV-WAN | RIPE | ASSIGNED PA | ● low |
| 213.191.98.0/24 | KTv-UnO | RIPE | ASSIGNED PA | ● low |
| 213.191.107.0/24 | KTv-UnO | RIPE | ASSIGNED PA | ● low |
| 2a03:7c00:9::/48 | KTV-VH | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
40.0%
of checked blocks have valid RPKI ROA coverage
(8 of 20)
Possible discrepancies (3)
These blocks are registered to KTV TELECOM but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a03:7c00:9::/48 /48 | authorized for AS199087 — KaseNet Oy |
| 213.191.107.0/24 /24 | authorized for AS29208 — Quantcom, a.s. |
| 213.191.98.0/24 /24 | authorized for AS29208 — Quantcom, a.s. |
NIC Handles
AS58158
DIALTELECOM-MNT
DUMY-RIPE
DUMY-RIPE
Kar36-MNT
Kcr1-MNT
TDK-MNT