TELESET-KAZAN
Cluster stats
Netblocks9
All fragments 65 blocks across 7 clusters
Cluster ID191954695
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 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.22.200.0/23 TELESET-KAZAN RIPE ASSIGNED PA ● low
81.22.202.0/23 TELESET-KAZAN RIPE ASSIGNED PA ● low
81.22.204.0/24 TELESET-KAZAN RIPE ASSIGNED PA ● low
81.22.205.0/24 TELESET-KAZAN RIPE ASSIGNED PA ● low
81.22.206.0/23 TELESET-KAZAN RIPE ASSIGNED PA ● low
81.22.208.0/22 TELESET-KAZAN RIPE ASSIGNED PA ● low
81.22.212.0/22 TELESET-KAZAN RIPE ASSIGNED PA ● low
87.117.160.0/20 TELESET-KAZAN RIPE ASSIGNED PA ● low
87.117.176.0/20 TELESET-KAZAN RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
77.8% of checked blocks have valid RPKI ROA coverage (7 of 9)
RPKI-inferred operator PJSC Rostelecom
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 TELESET-MNTNR