ixreport

INEX Route Collectors

AS2128 · Internet Neutral Exchange Association Ltd

INEX

3Exchanges
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Route CollectorType
OpenPeering policy
3Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with INEX Route Collectors? · Where should INEX Route Collectors peer next? · Compare INEX Route Collectors with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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.

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where INEX Route Collectors's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 12G across 3 exchanges.

Ireland INEX Cork Cork, Ireland 185.1.69.126 2001:7f8:18:210::126 1G Up, 0 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Ireland INEX LAN1 Dublin, Ireland 185.6.36.126 2001:7f8:18::f:0:1 1G 5 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Ireland INEX LAN2 Dublin, Ireland 194.88.240.2 2001:7f8:18:12::2 10G 5 routes Not in PeeringDB

INEX Route Collectors lists no facilities in PeeringDB.