megamax
Cluster stats
Netblocks12
All fragments 27 blocks across 8 clusters
Cluster ID193386116
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
196.46.25.166/32 megamax PEERINGDB ASSIGNED ● high
196.60.10.55/32 megamax PEERINGDB ASSIGNED ● high
196.60.70.130/32 megamax PEERINGDB ASSIGNED ● high
196.223.22.235/32 megamax PEERINGDB ASSIGNED ● high
2001:43f8:1f1::235/128 megamax PEERINGDB ASSIGNED ● high
2001:43f8:6d0::10:55/128 megamax PEERINGDB ASSIGNED ● high
2001:43f8:6d1::130/128 megamax PEERINGDB ASSIGNED ● high
31.7.224.0/21 MEGAMAX-NET RIPE ASSIGNED PA ● low
94.100.80.0/21 MEGAMAX-NET RIPE ASSIGNED PA ● low
94.100.88.0/21 MEGAMAX-NET RIPE ASSIGNED PA ● low
95.172.32.0/21 MEGAMAX-NET RIPE ASSIGNED PA ● low
95.172.40.0/21 MEGAMAX-NET RIPE ASSIGNED PA ● low

Network trust

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

NIC Handles

AS328237 DUMY-RIPE DUMY-RIPE MEGAMAX-MNT