ixreport

PLINQ: PeeringDB fix list

AS35224 · peeringdb.com/net/23185

PeeringDB

2 things to fix in PLINQ's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on PLINQ'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 (2)

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 AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:1::a503:5224:1
    • In the entry with IPv4 80.249.210.211: set IPv6 to 2001:7f8:1::a503:5224:1 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.116.52 193.239.119.79193.239.116.15 193.239.116.52 193.239.119.79
    IPv6 address missing from PeeringDBnone2001:7f8:13::a503:5224:1 2001:7f8:13::a503:5224:2 2001:7f8:13::a503:5224:3
    • In the entry with IPv4 193.239.116.52: set IPv6 to 2001:7f8:13::a503:5224:2 (now empty).
    • In the entry with IPv4 193.239.119.79: set IPv6 to 2001:7f8:13::a503:5224:3 (now empty).
    • Add an entry: IPv4 193.239.116.15, IPv6 2001:7f8:13::a503:5224:1, RS peer yes.

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