ixreport

Caudata Limited t/a Gigapeak

AS211175

3Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
3Using the route servers
4To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

Tools: Where can I peer with Caudata Limited t/a Gigapeak? · Where should Caudata Limited t/a Gigapeak peer next? · Compare Caudata Limited t/a Gigapeak with another network

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

PeeringDB fix list Printable page · CSV

4 things to fix in Caudata Limited t/a Gigapeak's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

AS211175 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

On the exchange's own member list, but not in Caudata Limited t/a Gigapeak's PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.231.202
    IPv62001:7f8:4::3:38e7:1
    Speed2000 Mbps (2G)
    RS peerYes
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321From its IX-F export and website members list
    IPv4195.66.236.5
    IPv62001:7f8:4:1:0:3:38e7:1
    Speed2000 Mbps (2G)
    RS peerYes
  3. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583From its IX-F export and website members list
    IPv4195.66.244.121
    IPv62001:7f8:4:2:0:3:38e7:1
    Speed2000 Mbps (2G)
    RS peerYes

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
    Address belongs to another network in PeeringDB195.66.236.5 is AS397601 Catchpoint195.66.236.5

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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 Caudata Limited t/a Gigapeak'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 6G across 3 exchanges.

United Kingdom LINX LON1 London, United Kingdom 195.66.231.202 2001:7f8:4::3:38e7:1 2G 2 routes Not in PeeringDB
United Kingdom LINX LON2 London, United Kingdom 195.66.236.5 2001:7f8:4:1::3:38e7:1 2G 2 routes Not in PeeringDB Address taken
United Kingdom LINX Manchester Manchester, United Kingdom 195.66.244.121 2001:7f8:4:2::3:38e7:1 2G 1 routes Not in PeeringDB