Bloomberg: PeeringDB fix list
AS10361 · peeringdb.com/net/20442
3 things to fix in Bloomberg'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 Bloomberg'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 IPv4 address missing from PeeringDB 195.66.227.137 195.66.227.137 195.66.227.217 IPv6 address missing from PeeringDB none 2001:7f8:4::2879:1 2001:7f8:4::2879:2 Port speed differs 100G 2 × 10G - In the entry with IPv4 195.66.227.137: set IPv6 to 2001:7f8:4::2879:1 (now empty); set Speed to 10000 (10G) (now 100000).
- Add an entry: IPv4 195.66.227.217, IPv6 2001:7f8:4::2879:2, speed 10000 (10G), RS peer yes.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:43f8:6d0::11:65 2001:43f8:6d0::11:66 - In the entry with IPv4 196.60.11.65: set IPv6 to 2001:43f8:6d0::11:65 (now empty).
- In the entry with IPv4 196.60.11.66: set IPv6 to 2001:43f8:6d0::11:66 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Bloomberg has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
DE-CIX New York New York, United States · PeeringDB 804Not on its IX-F export or website members listIPv4 206.82.104.159 IPv6 – Speed 100000 Mbps (100G) IPv4 206.82.104.200 IPv6 – Speed 100000 Mbps (100G)
From ixreport.com/net/10361/: 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.