Transtelecom Kazakhstan
Cluster stats
| Netblocks | 30 |
| All fragments | 61 blocks across 6 clusters |
| Cluster ID | 191993377 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.79.213.3/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.116.14/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.117.14/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.118.36/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.118.69/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.118.102/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.118.131/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.118.195/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.118.233/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.119.36/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.12.119.71/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.79/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 195.208.208.219/32 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:a::14/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:b::14/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:d::36/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:e::69/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:f::21/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:10::131/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:11::3/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:12::4/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:13::36/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:67c:9e8:14::71/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:79/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::208:219/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 2a01:7640:9400::3/128 | Transtelecom Kazakhstan | PEERINGDB | ASSIGNED | ● high |
| 81.4.192.0/22 | TRANSTELECOM-NN | RIPE | ASSIGNED PA | ● low |
| 81.18.128.0/23 | TRANSTELECOM-NN | RIPE | ASSIGNED PA | ● low |
| 81.18.148.0/24 | TRANSTELECOM-NN | RIPE | ASSIGNED PA | ● low |
| 91.185.31.0/24 | Transtelecom_IP | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
26.7%
of checked blocks have valid RPKI ROA coverage
(8 of 30)
Possible discrepancies (3)
These blocks are registered to Transtelecom Kazakhstan but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 81.4.192.0/22 /22 | authorized for AS15774 — Limited Liability Company "TTK-Svyaz" |
| 81.18.128.0/23 /23 | authorized for AS15774 — Limited Liability Company "TTK-Svyaz" |
| 81.18.148.0/24 /24 | authorized for AS15774 — Limited Liability Company "TTK-Svyaz" |
NIC Handles
AS41798
DUMY-RIPE
DUMY-RIPE
MNT-TTCP
VTT-MNT