MyComms: PeeringDB fix list

AS208833 · peeringdb.com/net/32479

2 things to fix in MyComms's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 18:53 UTC.

Make the changes on MyComms's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in MyComms's PeeringDB record. Add one entry per connection with these values.

LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list

IPv4 195.66.231.66

IPv6 2001:7f8:4::3:2fc1:1

Speed 10000 Mbps (10G)

RS peer No
LINX LON2 London, United Kingdom · PeeringDB 321From its IX-F export and website members list

IPv4 195.66.236.245

IPv6 2001:7f8:4:1:0:3:2fc1:1

Speed 10000 Mbps (10G)

RS peer No

IPv4	195.66.231.66
IPv6	2001:7f8:4::3:2fc1:1
Speed	10000 Mbps (10G)
RS peer	No

IPv4	195.66.236.245
IPv6	2001:7f8:4:1:0:3:2fc1:1
Speed	10000 Mbps (10G)
RS peer	No

From ixreport.com/net/208833/: 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.