BALTNET-NET
Cluster stats
| Netblocks | 23 |
| Cluster ID | 192265852 |
| Registry | RIPE |
| Customers | find 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 (23)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.190.254.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● high |
| 89.190.255.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● high |
| 89.190.224.0/20 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 89.190.240.0 – 89.190.248.255 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 89.190.249.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 89.190.250.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 89.190.251.0 – 89.190.252.255 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 89.190.253.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.65.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.66.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.67.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.68.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.69.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.70.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.71.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.72.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.73.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.74.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.75.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.76.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.77.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.78.0/24 | BALTNET-NET | RIPE | ASSIGNED PA | ● low |
| 217.168.79.0/24 | BALTNET-NET | 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
(23 of 23)
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
BALTNET-MNT
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT