PTCOMMNET
Cluster stats
Netblocks16
Cluster ID192170656
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 (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.108.192.0/20 PTCOMMNET RIPE ASSIGNED PA ● high
77.108.208.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
77.108.216.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
77.108.224.0/20 PTCOMMNET RIPE ASSIGNED PA ● high
77.108.240.0/20 PTCOMMNET RIPE ASSIGNED PA ● high
82.209.64.0/19 PTCOMMNET RIPE ASSIGNED PA ● high
85.234.32.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
85.234.40.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
85.234.48.0/20 PTCOMMNET RIPE ASSIGNED PA ● high
92.246.160.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
92.246.168.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
92.246.176.0/20 PTCOMMNET RIPE ASSIGNED PA ● high
95.83.64.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
95.83.72.0/21 PTCOMMNET RIPE ASSIGNED PA ● high
95.83.80.0/20 PTCOMMNET RIPE ASSIGNED PA ● high
95.83.96.0/19 PTCOMMNET RIPE ASSIGNED PA ● high

Network trust

what's this?
RPKI hygiene: F how networks compare →
18.8% of checked blocks have valid RPKI ROA coverage (3 of 16)
RPKI-inferred operator MTS PJSC
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 PENZATELECOM-MNT