TTK-Izhevsk
Cluster stats
Netblocks9
All fragments 275 blocks across 128 clusters
Cluster ID193037708
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.4.196.0/22 TTK-Izhevsk RIPE ASSIGNED PA ● low
81.4.212.0/22 TTK-Izhevsk RIPE ASSIGNED PA ● low
81.4.233.0/24 TTK-Izhevsk RIPE ASSIGNED PA ● low
81.4.235.0 – 81.4.237.255 TTK-Izhevsk RIPE ASSIGNED PA ● low
81.4.240.0/24 TTK-Izhevsk RIPE ASSIGNED PA ● low
81.4.250.0 – 81.4.253.255 TTK-Izhevsk RIPE ASSIGNED PA ● low
188.168.97.0/24 TTK-Izhevsk RIPE ASSIGNED PA ● low
188.168.188.0/23 TTK-Izhevsk RIPE ASSIGNED PA ● low
2a03:3700:5000::/36 TTK-Izhevsk RIPE ALLOCATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
RPKI-inferred operator Limited Liability Company "TTK-Svyaz"
Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TTK VTT-MNT