FUZE: PeeringDB fix list
AS13896 · peeringdb.com/net/11775
3 things to fix in FUZE's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on FUZE'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 (1)
On the exchange's own member list, but not in FUZE's PeeringDB record. Add one entry per connection with these values.
-
LINX Manchester Manchester, United Kingdom · PeeringDB 583From its IX-F export and website members listIPv4 195.66.244.152 IPv6 2001:7f8:4:2::3648:1 Speed 10000 Mbps (10G) RS peer Yes
Correct these entries (2)
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 Port speed differs 1G 10G - In the entry with IPv4 195.66.227.97: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:504:31::3648:1 Port speed differs 1G 10G - In the entry with IPv4 206.55.196.60: set IPv6 to 2001:504:31::3648:1 (now empty); set Speed to 10000 (10G) (now 1000).
From ixreport.com/net/13896/: 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.