TNPKO

BGP inherited
Cluster stats
Netblocks9 · 3,831 IPv4 addresses
Cluster ID209198467
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.23.144.0/24 TNPKO RIPE ASSIGNED PA ● high
81.23.145.0/24 TNPKO RIPE ASSIGNED PA ● high
81.23.147.0/24 TNPKO RIPE ASSIGNED PA ● high
81.23.148.0/23 TNPKO RIPE ASSIGNED PA ● high
81.23.150.0/23 TNPKO RIPE ASSIGNED PA ● high
81.23.152.0/22 TNPKO RIPE ASSIGNED PA ● high
81.23.156.0/24 TNPKO RIPE ASSIGNED PA ● high
81.23.157.0/24 TNPKO RIPE ASSIGNED PA ● high
81.23.158.0/23 TNPKO RIPE ASSIGNED PA ● high

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 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 MNT-TNPKO