YUGRATELECOM
Cluster stats
| Netblocks | 10 |
| Cluster ID | 192066181 |
| 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 (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.170.32.0/22 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 31.170.36.0/22 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 94.125.40.0/22 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 94.125.44.0/22 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 130.0.216.0/22 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 130.0.220.0/22 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 217.115.176.0 – 217.115.183.31 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 217.115.183.32 – 217.115.183.255 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 217.115.184.0 – 217.115.186.255 | YUGRATELECOM | RIPE | ASSIGNED PA | ● low |
| 217.115.187.0 – 217.115.191.255 | YUGRATELECOM | 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
(10 of 10)
RPKI-inferred operator
PJSC MegaFon
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
TI-MNT