margau Research Network: PeeringDB fix list

AS213204 · peeringdb.com/net/23463

PeeringDB

One thing to fix in margau Research Network's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 21:35 UTC.

Make the changes on margau Research Network'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. Germany KleyReX Frankfurt, Germany · PeeringDB 123
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone193.189.83.56
    • In the entry with IPv6 2001:7f8:33::a121:3204:1: set IPv4 to 193.189.83.56 (now empty).

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