Moscow
Registry
Cluster stats
| Netblocks | 2 |
| All fragments | 57 blocks across 33 clusters |
| Cluster ID | 191302387 |
| Registry | AFRINIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 95.167.232.0/21 | Moscow | RIPE | SUB-ALLOCATED PA | ● low |
| 102.38.250.0/23 | Moscow | AFRINIC | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
Possible discrepancies (1)
These blocks are registered to Moscow but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 95.167.232.0/21 /21 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
AA225-AFRINIC
DUMY-RIPE
DUMY-RIPE
ERO1-AFRINIC
ROSTELECOM-MNT
TSL10-MNT