Teknet Veri Merkezi: PeeringDB fix list

AS7768 · peeringdb.com/net/41308

PeeringDB

4 things to fix in Teknet Veri Merkezi's PeeringDB record, from what its exchanges publish: 1 to correct, 3 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Teknet Veri Merkezi's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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.

  1. Türkiye DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.48.36: set Speed to 100000 (100G) (now 10000).

Check these entries (3)

In PeeringDB, but on none of the exchange's own lists. If Teknet Veri Merkezi has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214Not on its IX-F export or website members list
    IPv4185.1.170.145
    IPv62001:7f8:9e:0:3:20c2:0:1
    Speed100000 Mbps (100G)
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74Not on its IX-F export or website members list
    IPv4185.1.210.149
    IPv62001:7f8:3d:0:3:20c2:0:1
    Speed100000 Mbps (100G)
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248Not on its IX-F export or website members list
    IPv4185.1.208.146
    IPv62001:7f8:44:0:3:20c2:0:1
    Speed100000 Mbps (100G)

From ixreport.com/net/7768/: 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.