INEX Route Collectors: PeeringDB fix list

AS2128 · peeringdb.com/net/502

PeeringDB

3 things to fix in INEX Route Collectors's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on INEX Route Collectors's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in INEX Route Collectors's PeeringDB record. Add one entry per connection with these values.

  1. Ireland INEX LAN2 Dublin, Ireland · PeeringDB 387From its IX-F export
    IPv4194.88.240.2
    IPv62001:7f8:18:12::2
    Speed10000 Mbps (10G)
    RS peerYes

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

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. Ireland INEX Cork Cork, Ireland · PeeringDB 1262
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.69.126185.1.69.2 185.1.69.49 185.1.69.126
    IPv6 address missing from PeeringDB2001:7f8:18:210::1262001:7f8:18:210::2 2001:7f8:18:210::126
    Port speed differs1G3 × 1G
    • Add an entry: IPv4 185.1.69.2, IPv6 2001:7f8:18:210::2, speed 1000 (1G), RS peer no.
    • Add an entry: IPv4 185.1.69.49, IPv6 –, speed 1000 (1G), RS peer no.

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

  2. Ireland INEX LAN1 Dublin, Ireland · PeeringDB 48
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.6.36.126185.6.36.2 185.6.36.126
    IPv6 address missing from PeeringDB2001:7f8:18::f:0:12001:7f8:18::2 2001:7f8:18::f:0:1
    Port speed differs1G10G + 1G
    • Add an entry: IPv4 185.6.36.2, IPv6 2001:7f8:18::2, speed 10000 (10G), 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/2128/: 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.