ixreport

Netlojik Bilgi Teknolojileri: PeeringDB fix list

AS202294 · peeringdb.com/net/41343

PeeringDB

3 things to fix in Netlojik Bilgi Teknolojileri's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-10-08 22:13 UTC.

Make the changes on Netlojik Bilgi Teknolojileri'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. United States EVIX Fremont, United States · PeeringDB 2274
    ProblemPeeringDB hasThe export has
    Port speed differs10G1G
    • In the entry with IPv4 206.81.104.16: set Speed to 1000 (1G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (2)

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

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.228.64
    IPv62001:7f8:4::3:1636:1
    Speed4000 Mbps (4G)
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.237.18
    IPv62001:7f8:4:1:0:3:1636:1
    Speed4000 Mbps (4G)

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