SPBTLG
Cluster stats
Netblocks16
Cluster ID195187137
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
213.158.0.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.1.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.2.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.3.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.4.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.5.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.6.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.7.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.8.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.9.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.10.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.11.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.12.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.13.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.14.0/24 SPBTLG RIPE ASSIGNED PA ● low
213.158.15.0/24 SPBTLG RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (16 of 16)
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

AS8997-MNT DUMY-RIPE DUMY-RIPE