ERTURK Can

BGP inherited
Cluster stats
Netblocks9
Cluster ID210850356
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
51.77.78.64/27 ERTURK Can RIPE LEGACY ● high
51.89.76.240/29 ERTURK Can RIPE LEGACY ● high
51.89.126.224/27 ERTURK Can RIPE LEGACY ● high
51.178.189.208/28 ERTURK Can RIPE LEGACY ● high
79.137.17.52/30 ERTURK Can RIPE ASSIGNED PA ● high
135.125.208.240/28 ERTURK Can RIPE ASSIGNED PA ● high
141.95.83.192/30 ERTURK Can RIPE ASSIGNED PA ● high
162.19.186.192/27 ERTURK Can RIPE LEGACY ● high
178.32.198.96/28 ERTURK Can RIPE ASSIGNED PA ● high

Possibly related to this organisation

what's this?
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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ORG-EC107-RIPE OVH-MNT