ixreport

VERSADC: PeeringDB fix list

AS219521 · peeringdb.com/net/43298

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

Make the changes on VERSADC'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
    Port speed differs100G1G
    • In the entry with IPv4 95.133.136.36: set Speed to 1000 (1G) (now 100000).

    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/219521/: 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.