MDNET

Handle
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID213185719
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
206.51.7.232/32 MDNET PEERINGDB ASSIGNED ● high
206.53.206.154/32 MDNET PEERINGDB ASSIGNED ● high
206.80.238.134/32 MDNET PEERINGDB ASSIGNED ● high
206.81.80.104/32 MDNET PEERINGDB ASSIGNED ● high
2001:504:16::9cca/128 MDNET PEERINGDB ASSIGNED ● high
2001:504:1b:1::232/128 MDNET PEERINGDB ASSIGNED ● high
2001:504:91::134/128 MDNET PEERINGDB ASSIGNED ● high
2606:a980:0:e::1a/128 MDNET PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MDNET” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.
  • UKMD sub-allocation
  • RARBMDNET-EMIRNET via EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC sub-allocation

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS40138