MAO
Cluster stats
Netblocks16
All fragments 58 blocks across 33 clusters
Cluster ID191798424
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
16 0 netblocks since 2026-07-05
2026-07-05 peak 16 2026-07-06

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.82.152/32 MAO PEERINGDB ASSIGNED ● high
185.0.27.74/32 MAO PEERINGDB ASSIGNED ● high
185.1.136.21/32 MAO PEERINGDB ASSIGNED ● high
185.1.240.82/32 MAO PEERINGDB ASSIGNED ● high
193.189.83.101/32 MAO PEERINGDB ASSIGNED ● high
193.239.118.212/32 MAO PEERINGDB ASSIGNED ● high
2001:7f8:13::a503:9526:1/128 MAO PEERINGDB ASSIGNED ● high
2001:7f8:17::9a66:1/128 MAO PEERINGDB ASSIGNED ● high
2001:7f8:33::a103:9526:1/128 MAO PEERINGDB ASSIGNED ● high
2001:7f8:da:0:185:1:136:21/128 MAO PEERINGDB ASSIGNED ● high
2001:7f8:12a::82/128 MAO PEERINGDB ASSIGNED ● high
2001:7f8:15e::74/128 MAO PEERINGDB ASSIGNED ● high
85.238.97.72/29 MAO RIPE ASSIGNED PA ● low
85.238.101.64/28 MAO RIPE ASSIGNED PA ● low
193.2.211.200/29 MAO-NET RIPE ASSIGNED PA ● low
2001:1470:ec56::/48 MAO-NET RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
81.2% of checked blocks have valid RPKI ROA coverage (13 of 16)
Possible discrepancies (1)

These blocks are registered to MAO 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.

2001:1470:ec56::/48 /48 authorized for AS2107 — ARNES

NIC Handles

ARNES-MNT AS39526 AS6876-MNT DUMY-RIPE DUMY-RIPE