Fastweb: PeeringDB fix list
AS12874 · peeringdb.com/net/1304
4 things to fix in Fastweb's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Fastweb'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 (4)
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 100G 200G - In the entry with IPv4 185.1.114.34: set Speed to 200000 (200G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 200G 300G - In the entry with IPv4 193.201.28.16: set Speed to 300000 (300G) (now 200000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 194.116.96.8: set Speed to 100000 (100G) (now 10000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:7f8:5f:ffff::3 none - In the entry with IPv4 185.1.115.3: set IPv6 to (empty) (now 2001:7f8:5f:ffff::3).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
From ixreport.com/net/12874/: 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.