ROSNET-DEVICES
Cluster stats
| Netblocks | 19 |
| All fragments | 123 blocks across 11 clusters |
| Cluster ID | 191955029 |
| Registry | RIPE |
| Customers | find 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 (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 86.111.10.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.134.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.135.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.137.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.139.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.140.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.142.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.143.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.144.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.145.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.147.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.152.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.153.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.154.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.90.190.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.96.168.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.96.176.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.96.178.0/24 | ROSNET-DEVICES | RIPE | ASSIGNED PA | ● low |
| 195.96.189.0/24 | ROSNET-DEVICES | 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
(19 of 19)
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
ROSNET-NOC