Caudata Limited t/a Gigapeak: PeeringDB fix list
AS211175
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-10-08 18:53 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.
-
IPv4 195.66.231.202 IPv6 2001:7f8:4::3:38e7:1 Speed 2000 Mbps (2G) RS peer Yes -
IPv4 195.66.236.5 IPv6 2001:7f8:4:1:0:3:38e7:1 Speed 2000 Mbps (2G) RS peer Yes -
LINX Manchester Manchester, United Kingdom · PeeringDB 583From its IX-F export and website members listIPv4 195.66.244.121 IPv6 2001:7f8:4:2:0:3:38e7:1 Speed 2000 Mbps (2G) RS peer Yes
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.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 195.66.236.5 is AS397601 Catchpoint 195.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.
From ixreport.com/net/211175/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.