ixreport

Connexin Limited

AS199775

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
5Using the route servers
5To fix in PeeringDB
3Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

5 things to fix in Connexin Limited's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Connexin 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 (5)

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 IXLeeds Leeds / Western Yorkshire, United Kingdom · PeeringDB 435
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:67::3:c5f:1
    • In the entry with IPv4 91.217.231.33: set IPv6 to 2001:7f8:67::3:c5f:1 (now empty).
  2. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::3:c5f:2
    • In the entry with IPv4 195.66.225.117: set IPv6 to 2001:7f8:4::3:c5f:2 (now empty).
  3. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:1:0:3:c5f:1
    • In the entry with IPv4 195.66.237.117: set IPv6 to 2001:7f8:4:1:0:3:c5f:1 (now empty).
  4. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4:2:0:3:c5f:1
    • In the entry with IPv4 195.66.244.16: set IPv6 to 2001:7f8:4:2:0:3:c5f:1 (now empty).
  5. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:17::3:c5f:1
    • In the entry with IPv4 5.57.82.130: set IPv6 to 2001:7f8:17::3:c5f:1 (now empty).

    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

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

Map

Where Connexin 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 270G across 5 exchanges.

United Kingdom IXLeeds Leeds / Western Yorkshire, United Kingdom 91.217.231.33 10G Yes Both IPv6 not in PeeringDB
United Kingdom LINX LON1 London, United Kingdom 195.66.225.117 20G 15 routes Both IPv6 not in PeeringDB
United Kingdom LINX LON2 London, United Kingdom 195.66.237.117 40G 15 routes Both IPv6 not in PeeringDB
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.16 100G 15 routes Both IPv6 not in PeeringDB
United Kingdom LONAP London, United Kingdom 5.57.82.130 100G 15 routes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where Connexin Limited lists itself in PeeringDB, but don't have Connexin 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)
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands North)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands North)
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 MA3 - Manchester, Joule House
Türkiye EURASIA-IX.NETIstanbul, Türkiye 6 Telehouse - London (Docklands North)
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands North)
Facilities (3)

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

United Kingdom Telehouse - London (Docklands North)London 3 of 11
United Kingdom Equinix MA3 - Manchester, Joule HouseManchester 1 of 2
United Kingdom aql DC2Leeds 1 of 1