ixreport

TransitX

AS35200 · TransitX

TransitX Ltd

4Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
4Using the route servers
1To fix in PeeringDB
6Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in TransitX's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on TransitX'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 LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB5.57.81.1675.57.81.166 5.57.81.167
    IPv6 address missing from PeeringDB2001:7f8:17::8980:22001:7f8:17::8980:2 2001:7f8:17::a74f:1
    Port speed differs40G100G + 40G
    • Add an entry: IPv4 5.57.81.166, IPv6 2001:7f8:17::a74f:1, speed 100000 (100G), 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

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

Map

Where TransitX'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 200G across 4 exchanges.

Netherlands ERA-IX Amsterdam Amsterdam, Netherlands 185.1.240.190 2001:7f8:12a::190 100G Yes PeeringDB only
United Kingdom LINX LON1 London, United Kingdom 195.66.228.97 2001:7f8:4::8980:2 50G 726 routes Both
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.142 2001:7f8:4:2::8980:1 10G 673 routes Both
United Kingdom LONAP London, United Kingdom 5.57.81.167 2001:7f8:17::8980:2 40G 1,403 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs

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

These exchanges have a switch in a facility where TransitX lists itself in PeeringDB, but don't have TransitX 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 AMS-IXAmsterdam, Netherlands 920 Iron Mountain Data Center - Amsterdam (AMS-1)
Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Telehouse - London (Docklands East); Telehouse - London (Docklands West); Iron Mountain Data Center - Amsterdam (AMS-1) and 1 more
United Kingdom LINX LON2London, United Kingdom 315 Telehouse - London (Docklands East); Telehouse - London (Docklands West); Telehouse - London (Docklands North Two)
Germany LOCIX FRANKFURTFrankfurt am Main, Germany 205 Iron Mountain Data Center - Amsterdam (AMS-1)
Bulgaria NetIXSofia, Bulgaria 204 Telehouse - London (Docklands East); Telehouse - London (Docklands West); Iron Mountain Data Center - Amsterdam (AMS-1)
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Telehouse - London (Docklands East); Telehouse - London (Docklands West); Telehouse - London (Docklands North Two)
Netherlands Clue-IXAmsterdam, Netherlands 36 Iron Mountain Data Center - Amsterdam (AMS-1)
United Kingdom Equinix ManchesterManchester, United Kingdom 19 Equinix MA1 - Manchester, Williams/Kilburn
Sweden KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden 11 Iron Mountain Data Center - Amsterdam (AMS-1)
United Kingdom IXMidlandsWolverhampton, United Kingdom 7 UK Servers Coventry
United States Global Peer ExchangeWashington, United States 6 Telehouse - London (Docklands West); Iron Mountain Data Center - Amsterdam (AMS-1)
Germany TMW-iXFrankfurt am Main, Germany 5 Iron Mountain Data Center - Amsterdam (AMS-1)
Australia ixFabricGlobal, Australia 2 Iron Mountain Data Center - Amsterdam (AMS-1)
Facilities (6)

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