SB: PeeringDB fix list
AS24013 · peeringdb.com/net/17265
4 things to fix in SB's PeeringDB record, from what its exchanges publish: 3 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on SB'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 (3)
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 100G - In the entry with IPv4 80.81.195.98: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.210.138: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.208.138: set Speed to 100000 (100G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If SB has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214Not on its IX-F export or website members listIPv4 185.1.171.16 IPv6 2001:7f8:9e::1859:0:2 Speed 10000 Mbps (10G)
From ixreport.com/net/24013/: 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.