ixreport

Daniel Piekacz: PeeringDB fix list

AS212196 · peeringdb.com/net/25408

PeeringDB

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

Make the changes on Daniel Piekacz'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. ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.125.57
    • In the entry with IPv6 2001:7f8:d0::3:3ce4:1: set IPv4 to 185.1.125.57 (now empty).

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