MARTIN-DAWES-SYSTEMS

BGP inherited

Cluster stats

Netblocks	4
All fragments	7 blocks across 4 clusters
Cluster ID	204658934
Registry	RIPE
Customers	find 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

IP Ranges (4)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
80.168.55.0/25	MARTIN-DAWES-SYSTEMS	RIPE	ASSIGNED PA	● low
80.168.151.112/29	MARTIN-DAWES-SYSTEMS	RIPE	ASSIGNED PA	● low
194.168.243.88/30	MARTIN-DAWES-SYSTEMS-LTD	RIPE	ASSIGNED PA	● low
217.158.205.224/27	MARTIN-DAWES-SYSTEMS	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “MARTIN DAWES” — 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.

MARTINDAWES-VDS-NET sub-allocation
Martin Dawes via MAINFRAME & CYBERNETIC SYSTEMS LIMITED sub-allocation
MARTIN-DAWES-IVCLTD01 sub-allocation
MARTINDAWESTELECOMMUNICATION via Eircom Limited sub-allocation
MARTIN-DAWES-EUROPA-OPAL via Vercara, LLC sub-allocation
MARTINDAWESSYSTEMS via Eircom Limited sub-allocation
MARTIN-DAWES-LIMITED via Claranet Limited sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (4 of 4)

No discrepancies found among checked blocks.

NIC Handles

AS5089-MNT AS8426-MNT DUMY-RIPE DUMY-RIPE