ixreport

Ramtek: PeeringDB fix list

AS29399 · peeringdb.com/net/20918

One thing to fix in Ramtek's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Ramtek'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 RegPEX Ankara, Türkiye · PeeringDB 4986
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB95.133.136.4195.133.136.41 95.133.136.42
    IPv6 address missing from PeeringDB2001:7f8:171::292001:7f8:171::29 2001:7f8:171::2a
    Port speed differs100G2 × 100G
    • Add an entry: IPv4 95.133.136.42, IPv6 2001:7f8:171::2a, speed 100000 (100G), RS peer yes.

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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