ixreport

Info-Connect: PeeringDB fix list

AS20618 · peeringdb.com/net/21182

PeeringDB

One thing to fix in Info-Connect's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-12 00:59 UTC.

Make the changes on Info-Connect'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. Denmark DIX Copenhagen, Denmark · PeeringDB 78
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:7f8:1f:0:2:618:99:0 2001:7f8:1f:0:2:618:100:02001:7f8:1f:1500::99 2001:7f8:1f:1500::100 2001:7f8:1f:9000::227 2001:7f8:1f:9000::228
    IPv4 address missing from PeeringDB192.38.7.99 192.38.7.100185.1.57.99 185.1.57.100 185.1.57.227 185.1.57.228 192.38.7.99 192.38.7.100
    Port speed differs2 × 10G3G
    • In the entry with IPv4 192.38.7.100: set IPv6 to (empty) (now 2001:7f8:1f:0:2:618:100:0); set Speed to 3000 (3G) (now 10000).
    • In the entry with IPv4 192.38.7.99: set IPv6 to (empty) (now 2001:7f8:1f:0:2:618:99:0); set Speed to 3000 (3G) (now 10000).
    • Add an entry: IPv4 185.1.57.99, IPv6 2001:7f8:1f:1500::99, speed 3000 (3G), RS peer yes.
    • Add an entry: IPv4 185.1.57.100, IPv6 2001:7f8:1f:1500::100, speed 3000 (3G), RS peer yes.
    • Add an entry: IPv4 185.1.57.227, IPv6 2001:7f8:1f:9000::227, speed 3000 (3G), RS peer yes.
    • Add an entry: IPv4 185.1.57.228, IPv6 2001:7f8:1f:9000::228, speed 3000 (3G), RS peer yes.

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