ixreport

ARTNET: PeeringDB fix list

AS197155 · peeringdb.com/net/16549

PeeringDB

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

Make the changes on ARTNET'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. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB212.91.0.214212.91.0.159 212.91.0.214
    Port speed differs10G20G
    • In the entry with IPv4 212.91.0.214: set IPv4 to (empty) (now 212.91.0.214); set Speed to 20000 (20G) (now 10000).
    • Add an entry: IPv4 212.91.0.159, IPv6 –, speed 20000 (20G).
    • Add an entry: IPv4 212.91.0.214, IPv6 –, speed 20000 (20G).

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