K-Telekom Sp. z o.o.
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 34 blocks across 2 clusters |
| Cluster ID | 205194354 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 94.246.179.24/31 | K-Telekom Sp. z o.o. | RIPE | ASSIGNED PA | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “K Telekom” — 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.
- K-telekom LLC 33 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.
- Rostelekom_Sibirskij_filial_TU-3 via PJSC Rostelecom sub-allocation
- Telekom-Sojuz_DVF via PJSC Rostelecom sub-allocation
- Penza-Telekom via PJSC Rostelecom sub-allocation
- Nalchik-telekom via PJSC Rostelecom sub-allocation
- Irbis_telekommunikejshns via PJSC Rostelecom sub-allocation
- Telekom via PJSC Rostelecom sub-allocation
- Kolambija-Telekom via PJSC Rostelecom sub-allocation
- Centralnyj_filial__Rostelekom via PJSC Rostelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
No discrepancies found among checked blocks.
NIC Handles
ART-COM-MNT
DUMY-RIPE
DUMY-RIPE
ORG-KTEL1-RIPE