Olfe Veri Merkezi - İzmir: PeeringDB fix list
AS200010 · peeringdb.com/net/42132
2 things to fix in Olfe Veri Merkezi - İzmir's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Olfe Veri Merkezi - İzmir'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 IPv6 address missing from PeeringDB none 2001:7f8:171::1a Port speed differs 20G 10G - In the entry with IPv4 95.133.136.26: set IPv6 to 2001:7f8:171::1a (now empty); set Speed to 10000 (10G) (now 20000).
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 (1)
In PeeringDB, but on none of the exchange's own lists. If Olfe Veri Merkezi - İzmir has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958Not on its website members listIPv4 185.0.43.254 IPv6 – Speed 100000 Mbps (100G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/200010/: 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.