TURKSAT
AS47524
Tools: Where can I peer with TURKSAT? · Where should TURKSAT peer next? · Compare TURKSAT with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
2 things to fix in TURKSAT's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on TURKSAT's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in TURKSAT's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export and website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Correct these entries (1)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.1.48.62 185.1.48.49 185.1.48.62 IPv6 address missing from PeeringDB 2001:7f8:3f::b9a4:0:1 2001:7f8:3f::b9a4:0:1 2001:7f8:3f::b9a4:0:2 Port speed differs 100G 2 × 100G - Add an entry: IPv4 185.1.48.49, IPv6 2001:7f8:3f::b9a4:0:2, speed 100000 (100G), RS peer no.
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
Map
Where TURKSAT's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| DE-CIX Istanbul Istanbul, Türkiye | 100G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| NetIX Sofia, Bulgaria | Not in PeeringDB | ||
| NetIX Greece Thessaloniki / Athens, Greece | 100G | PeeringDB |
These exchanges have a switch in a facility where TURKSAT lists itself in PeeringDB, but don't have TURKSAT as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.
| GIBIRIXİstanbul, Türkiye | 28 | |
| EURASIA-IX.NETIstanbul, Türkiye | 6 | |
| Global Peer ExchangeWashington, United States | 6 | |
| TurkIX IstanbulIstanbul, Türkiye | 3 |
Facilities (2)
The buildings TURKSAT lists in PeeringDB, and how many of the exchanges in each it's on.
| Equinix IL2 - IstanbulIstanbul | 1 of 5 | |
| MedNautilus IstanbulIstanbul | 2 of 4 |