TURKSAT: PeeringDB fix list
AS47524 · peeringdb.com/net/30260
2 things to fix in TURKSAT's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 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.
From ixreport.com/net/47524/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.