AAA-Azov-NET
Unresolved
Cluster stats
| Netblocks | 4 |
| All fragments | 82 blocks across 25 clusters |
| Cluster ID | 192097654 |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 77.66.162.0/24 | AAA-Azov-NET | RIPE | ASSIGNED PA | ● low |
| 77.66.241.0/24 | AAA-Azov-NET | RIPE | ASSIGNED PA | ● low |
| 94.77.146.0/24 | AAA-Azov-NET | RIPE | ASSIGNED PA | ● low |
| 213.27.32.0/24 | AAA-Azov-NET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
RPKI-inferred operator
MTS PJSC
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
KUBANGSM-MNT