TR-TURKNET

BGP inherited
Cluster stats
Netblocks8 · 556 IPv4 addresses
All fragments 19 blocks across 3 clusters
Cluster ID209527834
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

Footprint over time

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

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
31.223.82.0/24 TR-TURKNET RIPE ASSIGNED PA ● low
193.192.106.48/29 TR-TURKNET RIPE ASSIGNED PA ● low
212.125.11.0/24 TR-TURKNET RIPE ASSIGNED PA ● low
212.154.55.96/29 TR-TURKNET RIPE ASSIGNED PA ● low
212.154.58.64/30 TR-TURKNET RIPE ASSIGNED PA ● low
212.154.58.128/28 TR-TURKNET RIPE ASSIGNED PA ● low
212.154.83.32/29 TR-TURKNET RIPE ASSIGNED PA ● low
212.154.127.0/29 TR-TURKNET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TR TURKNET” — 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MNT-TURKNET-MNT