Sepehr Ahmadi: PeeringDB fix list
AS207609 · peeringdb.com/net/23101
2 things to fix in Sepehr Ahmadi's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Sepehr Ahmadi'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 (1)
On the exchange's own member list, but not in Sepehr Ahmadi's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::3:2af9:1 Speed Not published RS peer Yes
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 149.112.50.19 149.112.50.19 149.112.50.111 IPv6 address missing from PeeringDB 2001:504:125:e1::19 2001:504:125:e1::19 2001:504:125:e1::111 Port speed differs 10G 10G + 1G - Add an entry: IPv4 149.112.50.111, IPv6 2001:504:125:e1::111, speed 1000 (1G), RS peer yes.
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/207609/: 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.