Fusionnet Web Services: PeeringDB fix list
AS134375 · peeringdb.com/net/12918
3 things to fix in Fusionnet Web Services's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Fusionnet Web Services'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 (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 10G 2 × 100G - In the entry with IPv4 103.27.168.70: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G + 10G PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Fusionnet Web Services has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 45.120.248.48 IPv6 2001:df2:1900:1::48 Speed 100000 Mbps (100G)
From ixreport.com/net/134375/: 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.