MER002
Cluster stats
Netblocks16
Cluster ID191757966
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.101.139.68/30 MER002 RIPE ASSIGNED PA ● low
5.101.171.112/30 MER002 RIPE ASSIGNED PA ● low
37.9.59.8/30 MER002 RIPE ASSIGNED PA ● low
77.74.198.64/30 MER002 RIPE ASSIGNED PA ● low
77.75.121.76/30 MER002 RIPE ASSIGNED PA ● low
78.110.160.72/30 MER002 RIPE ASSIGNED PA ● low
78.157.192.0/29 MER002 RIPE ASSIGNED PA ● low
78.157.211.80/29 MER002 RIPE ASSIGNED PA ● low
78.157.218.160/27 MER002 RIPE ASSIGNED PA ● low
94.46.195.140/30 MER002 RIPE ASSIGNED PA ● low
94.229.78.96/28 MER002 RIPE ASSIGNED PA ● low
178.159.2.180/30 MER002 RIPE ASSIGNED PA ● low
178.159.3.196/30 MER002 RIPE ASSIGNED PA ● low
178.159.13.192/26 MER002 RIPE ASSIGNED PA ● low
2a01:a500:2444:f0f::/64 MER002 RIPE ASSIGNED ● low
2a01:a500:2771::/48 MER002 RIPE AGGREGATED-BY-LIR ● low

Network trust

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

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

2a01:a500:2771::/48 /48 authorized for AS42831 — UK Dedicated Servers Limited

NIC Handles

DUMY-RIPE DUMY-RIPE UKSERVERS-MNT