INEX Route Collectors
AS2128 · Internet Neutral Exchange Association Ltd
INEX
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.
-
IPv4 194.88.240.2 IPv6 2001:7f8:18:12::2 Speed 10000 Mbps (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.
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.1.69.126 185.1.69.2 185.1.69.49 185.1.69.126 IPv6 address missing from PeeringDB 2001:7f8:18:210::126 2001:7f8:18:210::2 2001:7f8:18:210::126 Port speed differs 1G 3 × 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 185.6.36.126 185.6.36.2 185.6.36.126 IPv6 address missing from PeeringDB 2001:7f8:18::f:0:1 2001:7f8:18::2 2001:7f8:18::f:0:1 Port speed differs 1G 10G + 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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 3 |
| Nov 18, 2026 | 3 |
| Nov 17, 2026 | 3 |
| Nov 16, 2026 | 3 |
| Nov 15, 2026 | 3 |
| Nov 14, 2026 | 3 |
| Nov 13, 2026 | 3 |
| Nov 12, 2026 | 3 |
| Nov 11, 2026 | 3 |
| Nov 10, 2026 | 3 |
| Nov 9, 2026 | 3 |
| Nov 8, 2026 | 3 |
| Nov 7, 2026 | 3 |
| Nov 6, 2026 | 3 |
| Nov 5, 2026 | 3 |
| Nov 4, 2026 | 3 |
| Nov 3, 2026 | 3 |
| Nov 2, 2026 | 3 |
| Nov 1, 2026 | 3 |
| Oct 31, 2026 | 3 |
| Oct 30, 2026 | 3 |
| Oct 29, 2026 | 3 |
| Oct 28, 2026 | 3 |
| Oct 27, 2026 | 3 |
| Oct 26, 2026 | 3 |
| Oct 25, 2026 | 3 |
| Oct 24, 2026 | 3 |
| Oct 23, 2026 | 3 |
| Oct 22, 2026 | 3 |
| Oct 21, 2026 | 3 |
| Oct 20, 2026 | 3 |
| Oct 19, 2026 | 3 |
| Oct 18, 2026 | 3 |
| Oct 17, 2026 | 3 |
| Oct 16, 2026 | 3 |
| Oct 15, 2026 | 3 |
| Oct 14, 2026 | 3 |
| Oct 13, 2026 | 3 |
| Oct 12, 2026 | 3 |
| Oct 11, 2026 | 3 |
| Oct 10, 2026 | 3 |
| Oct 9, 2026 | 3 |
| Oct 8, 2026 | 3 |
| Oct 7, 2026 | 3 |
| Oct 6, 2026 | 3 |
| Oct 5, 2026 | 3 |
| Oct 4, 2026 | 3 |
| Oct 3, 2026 | 3 |
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.
| INEX Cork Cork, Ireland | 1G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| INEX LAN1 Dublin, Ireland | 1G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| INEX LAN2 Dublin, Ireland | 10G | Not in PeeringDB |
INEX Route Collectors lists no facilities in PeeringDB.