DE-CIX Istanbul Route Servers: PeeringDB fix list
AS20715 · peeringdb.com/net/8920
One thing to fix in DE-CIX Istanbul Route Servers's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on DE-CIX Istanbul Route Servers'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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 185.1.48.66 is AS214803 Brnchost Bilisim Teknolojileri 185.1.48.66 IPv6 address missing from PeeringDB 2001:7f8:3f::50eb:fc:1 2001:7f8:3f::50eb:fd:1 2001:7f8:3f::50eb:42:1 2001:7f8:3f::50eb:fc:1 2001:7f8:3f::50eb:fd:1 Port speed differs 2 × 10G 3 × 20G An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 185.1.48.252: set Speed to 20000 (20G) (now 10000).
- In the entry with IPv4 185.1.48.253: set Speed to 20000 (20G) (now 10000).
- Add an entry: IPv4 –, IPv6 2001:7f8:3f::50eb:42:1, speed 20000 (20G), RS peer no.
From ixreport.com/net/20715/: 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.