ixreport

DIGITURK LTD.: PeeringDB fix list

AS203182 · peeringdb.com/net/35730

PeeringDB

2 things to fix in DIGITURK LTD.'s PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 22:13 UTC.

Make the changes on DIGITURK LTD.'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 (2)

On the exchange's own member list, but not in DIGITURK LTD.'s PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    4 connections, so 4 entries:

    IPv4178.18.236.110
    IPv62a03:5f80:4:2::236:110
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.236.146
    IPv62a03:5f80:4:2::236:146
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.236.193
    IPv62a03:5f80:4:2::236:193
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.237.12
    IPv62a03:5f80:4:2::237:12
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From its IX-F export and website members list
    IPv4194.42.47.51
    IPv62001:7f8:161::51
    Speed100000 Mbps (100G)
    RS peerYes

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

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