SETUR

BGP inherited
Cluster stats
Netblocks6
Registered in FO (4) · Turkey (2)
All fragments 12 blocks across 5 clusters
Cluster ID208884486
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 4 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-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.87.65.160/27 SETUR RIPE ASSIGNED PA ● low
212.55.50.8/29 SETUR RIPE ASSIGNED PA ● low
212.55.53.92/30 Setur RIPE ASSIGNED PA ● low
212.55.53.100/30 Setur RIPE ASSIGNED PA ● low
212.55.56.136/30 setur RIPE ASSIGNED PA ● low
212.115.29.64/26 SETUR-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

DUMY-RIPE DUMY-RIPE FT-NET-MNT KOCNET-NCC