MARI-VOLGATELECOM
Cluster stats
| Netblocks | 18 |
| All fragments | 24 blocks across 6 clusters |
| Cluster ID | 193067197 |
| 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 (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 77.40.0.0/24 | MARI-VOLGATELECOM | RIPE | SUB-ALLOCATED PA | ● low |
| 77.40.1.0/24 | MARI-VOLGATELECOM | RIPE | SUB-ALLOCATED PA | ● low |
| 77.40.2.0 – 77.40.7.255 | MARI-VOLGATELECOM | RIPE | SUB-ALLOCATED PA | ● low |
| 77.40.8.0 – 77.40.79.255 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.96.0/22 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.100.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.101.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.102.0 – 77.40.111.255 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.112.0 – 77.40.114.255 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.115.0 – 77.40.117.255 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.118.0/23 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.120.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.121.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.122.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.123.0 – 77.40.124.255 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.125.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.126.0/24 | MARI-VOLGATELECOM | RIPE | ASSIGNED PA | ● low |
| 77.40.127.0/24 | MARI-VOLGATELECOM | 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
(18 of 18)
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
ROSTELECOM-MNT