Calltower: PeeringDB fix list
AS20340 · peeringdb.com/net/7703
4 things to fix in Calltower's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Calltower'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 (2)
On the exchange's own member list, but not in Calltower's PeeringDB record. Add one entry per connection with these values.
-
IPv4 80.249.214.181 IPv6 2001:7f8:1::a502:340:1 Speed 1000 Mbps (1G) RS peer No PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 195.66.231.36 IPv6 2001:7f8:4::4f74:1 Speed 1000 Mbps (1G) RS peer No
Correct these entries (1)
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 80.81.194.68 80.81.192.14 80.81.194.68 IPv6 address missing from PeeringDB none 2001:7f8::4f74:0:1 2001:7f8::4f74:0:2 Port speed differs 1G 2 × 10G - In the entry with IPv4 80.81.194.68: set IPv6 to 2001:7f8::4f74:0:2 (now empty); set Speed to 10000 (10G) (now 1000).
- Add an entry: IPv4 80.81.192.14, IPv6 2001:7f8::4f74:0:1, speed 10000 (10G), RS peer yes.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Calltower 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.105.64 IPv6 – Speed 1000 Mbps (1G)
From ixreport.com/net/20340/: 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.