MIT
Cluster stats
Netblocks9
All fragments 91 blocks across 24 clusters
Cluster ID191945327
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 16 shared RIR contact/maintainer handles
Registry names 6 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
210.14.10.32/27 MIT APNIC ASSIGNED NON-PORTABLE ● high
85.182.238.32/28 MIT-GMBH-NET RIPE ASSIGNED PA ● low
109.224.33.152/29 MIT RIPE ASSIGNED PA ● low
163.61.188.0/24 MIT APNIC ALLOCATED NON-PORTABLE ● low
178.20.184.144/28 MIT RIPE ASSIGNED PA ● low
185.155.84.64/26 MIT RIPE ASSIGNED PA ● low
194.77.211.104/29 MIT-net RIPE ASSIGNED PA ● low
212.143.243.136/29 NV-MIT RIPE ASSIGNED PA ● low
217.222.220.208/29 MIT-inc RIPE ASSIGNED PA ● low

Network trust

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

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

163.61.188.0/24 /24 authorized for AS153568 — NEW DHAKA HARDWARE

NIC Handles

CD182-AP DUMY-RIPE DUMY-RIPE JM540-AP MAINT-MIT-US MDA-Z MN1098-AP MN1098-AP MN1098-AP MNT-EARTH MNT-VTELJO NV-MNT-RIPE +4 more