DMM-FTTH

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks6 · 5,888 IPv4 addresses
All fragments 7 blocks across 2 clusters
Cluster ID215823701
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 · report an issue

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-12
2026-07-12 peak 6 2026-07-26

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.223.224.0/22 DMM-FTTH RIPE ASSIGNED PA ● low
79.139.92.0/24 DMM-FTTH RIPE ASSIGNED PA ● low
79.139.93.0/24 DMM-FTTH RIPE ASSIGNED PA ● low
95.178.48.0/21 DMM-FTTH RIPE ASSIGNED PA ● low
95.178.72.0/21 DMM-FTTH RIPE ASSIGNED PA ● low
95.178.86.0/24 DMM-FTTH 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 (6 of 6)
RPKI-inferred operator Mobile Telecommunication Company Saudi Arabia Joint-Stock company
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 MTCKSA-MNT