DVF_Khabarovsk_YOTA-mobile
Cluster stats
Netblocks12
All fragments 14 blocks across 2 clusters
Cluster ID194868487
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
188.162.230.0/23 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.234.0/23 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.237.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.238.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.239.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.240.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.241.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.242.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.243.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.244.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.245.0/24 DVF_Khabarovsk_YOTA-mobile RIPE ASSIGNED PA ● low
188.162.246.0/23 DVF_Khabarovsk_YOTA-mobile 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 (12 of 12)
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 GDC-TR-CoreIP MEGAFON-RIPE-MNT