K Telecom Ldt.
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 16 |
| IPv6 | 7 prefixes (largest 2001:7f8:20:101::210:234/128) |
| Registered in | Russia (5) · AG (3) |
| All fragments | 116 blocks across 7 clusters |
| Cluster ID | 222470140 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 | |
Footprint over time
8 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-08-16
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 |
IPv6 ranges (7)
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