MERTENS-NET

BGP inherited
Cluster stats
Netblocks6
Registered in Germany (4) · Netherlands (2)
All fragments 15 blocks across 6 clusters
Cluster ID209045206
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
2.207.204.192/29 MERTENS-NET RIPE ASSIGNED PA ● low
2.207.234.64/29 MERTENS-NET RIPE ASSIGNED PA ● low
176.94.21.40/29 MERTENS-NET RIPE ASSIGNED PA ● low
176.95.87.48/29 MERTENS-NET RIPE ASSIGNED PA ● low
193.172.181.168/29 MERTENS RIPE ASSIGNED PA ● low
193.173.120.176/29 MERTENS RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MERTENS” — 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.

Network trust

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

NIC Handles

ARCOR-MNT AS286-MNT DUMY-RIPE DUMY-RIPE