Türk Telekom International

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks34
IPv6 17 prefixes (largest 2001:67c:29f0::6663:1/128)
Registered in Czechia (2) · Netherlands (2) · Romania (2) · Germany (2) · Ukraine (2) · Bulgaria (2)
Cluster ID222462389
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

8 weekly snapshots · JSON
34 +4 netblocks since 2026-07-05
2026-07-05 peak 34 2026-08-16

IP Ranges (34)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.194.173/32 Türk Telekom International PEERINGDB ASSIGNED ● high
80.249.208.121/32 Türk Telekom International PEERINGDB ASSIGNED ● high
86.104.125.70/32 Türk Telekom International PEERINGDB ASSIGNED ● high
91.210.16.163/32 Türk Telekom International PEERINGDB ASSIGNED ● high
178.18.230.185/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.0.20.231/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.1.48.33/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.1.63.208/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.1.103.6/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.1.226.122/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.1.227.122/32 Türk Telekom International PEERINGDB ASSIGNED ● high
185.1.240.110/32 Türk Telekom International PEERINGDB ASSIGNED ● high
192.108.148.250/32 Türk Telekom International PEERINGDB ASSIGNED ● high
193.25.180.192/32 Türk Telekom International PEERINGDB ASSIGNED ● high
193.188.137.20/32 Türk Telekom International PEERINGDB ASSIGNED ● high
193.203.0.160/32 Türk Telekom International PEERINGDB ASSIGNED ● high
195.66.224.252/32 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:67c:29f0::6663:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:67c:29f0::6663:2/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8::dd93:0:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:1::a500:6663:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:4::1a07:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:14::32:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:2f::250/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:30:0:2:1:0:6663/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:35::6663:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:3f::1a07:0:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:49::6/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:63::c0/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:64:225::6663:1/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:6c::463/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:7f::231/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2001:7f8:12a::110/128 Türk Telekom International PEERINGDB ASSIGNED ● high
2a03:5f80:7::230:185/128 Türk Telekom International PEERINGDB ASSIGNED ● high

IPv6 ranges (17)

showing the 15 largest allocations

Network trust

what's this?
RPKI hygiene: C how networks compare →
61.8% of checked blocks have valid RPKI ROA coverage (21 of 34)
No discrepancies found among checked blocks.

NIC Handles

AS6663