ixreport

VASH DOHOD: PeeringDB fix list

AS205717 · peeringdb.com/net/17800

PeeringDB

One thing to fix in VASH DOHOD's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on VASH DOHOD'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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:87
    Port speed differs1.024G10G
    • In the entry with IPv4 178.18.225.87: set IPv6 to 2a03:5f80:4::225:87 (now empty); set Speed to 10000 (10G) (now 1024).

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