JSC InterDnestrCom (IDC): PeeringDB fix list
AS1547 · peeringdb.com/net/2895
4 things to fix in JSC InterDnestrCom (IDC)'s PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on JSC InterDnestrCom (IDC)'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 JSC InterDnestrCom (IDC)'s PeeringDB record. Add one entry per connection with these values.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members listIPv4 193.239.117.123 IPv6 2001:7f8:13::a500:1547:1 Speed Not published 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.
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 100G 50G - In the entry with IPv4 193.178.185.62: set Speed to 50000 (50G) (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 2G 100G - In the entry with IPv4 185.1.192.174: set Speed to 100000 (100G) (now 2000).
-
Problem PeeringDB has The export has Port speed differs 10G 3G - In the entry with IPv4 195.66.224.200: set Speed to 3000 (3G) (now 10000).
From ixreport.com/net/1547/: 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.