ixreport

IP River Limited

AS62163

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

Tools: Where can I peer with IP River Limited? · Where should IP River Limited peer next? · Compare IP River Limited with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in IP River Limited's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-11-19 18:41 UTC.

Make the changes on IP River Limited'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. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address differs2001:7f8:4:1::3172:12001:7f8:4:1::f2d3:1
    • In the entry with IPv4 195.66.237.154: set IPv6 to 2001:7f8:4:1::f2d3:1 (now 2001:7f8:4:1::3172:1).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If IP River Limited has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
    IPv4195.66.244.72
    IPv62001:7f8:4:2::f2d3:1
    Speed10000 Mbps (10G)

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 IP River Limited'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 30G across 3 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.225.154 2001:7f8:4::3172:1 10G Down Both
United Kingdom LINX LON2 London, United Kingdom 195.66.237.154 2001:7f8:4:1::3172:1 10G 25 routes Both IPv6 differs
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.72 2001:7f8:4:2::f2d3:1 10G Yes PeeringDB only

Exchanges in its buildings that it isn't on (10)

These exchanges have a switch in a facility where IP River Limited lists itself in PeeringDB, but don't have IP River Limited as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands GNM-IXAmsterdam, Netherlands 741 Telehouse - London (Docklands North)
Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands North); Telehouse - London (Docklands West)
United Kingdom LONAPLondon, United Kingdom 311 Telehouse - London (Docklands North); Telehouse - London (Docklands West)
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands North); Telehouse - London (Docklands West)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North); Telehouse - London (Docklands West)
United Kingdom Kent Internet Exchange PointKent, United Kingdom 102 Telehouse - London (Docklands North)
Romania Balcan-IXBucharest, Romania 29 Telehouse - London (Docklands North)
United Kingdom Equinix ManchesterManchester, United Kingdom 19 Equinix MA1 - Manchester, Williams/Kilburn
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Telehouse - London (Docklands North)
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands North); Telehouse - London (Docklands West)
Facilities (3)

The buildings IP River Limited lists in PeeringDB, and how many of the exchanges in each it's on.