OTT UKRAINE: PeeringDB fix list
AS204384 · peeringdb.com/net/21712
7 things to fix in OTT UKRAINE's PeeringDB record, from what its exchanges publish: 3 to add, 3 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on OTT UKRAINE'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 (3)
On the exchange's own member list, but not in OTT UKRAINE's PeeringDB record. Add one entry per connection with these values.
-
1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members listThe exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
2 connections, so 2 entries:
IPv4 89.46.144.18 IPv6 2001:678:3ac::18 Speed 100000 Mbps (100G) RS peer Yes IPv4 89.46.144.85 IPv6 2001:678:3ac::85 Speed 100000 Mbps (100G) 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.
-
Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713From its IX-F export and website members listIPv4 185.0.21.26 IPv6 2001:7f8:7f::c:26 Speed 12500 Mbps (12.5G) RS peer Yes
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 40G + 10G 2 × 100G - In the entry with IPv4 193.188.137.43: set Speed to 100000 (100G) (now 10000).
- In the entry with IPv4 193.188.137.83: set Speed to 100000 (100G) (now 40000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:14::d6:1 2001:7f8:14::d6:2 - In the entry with IPv4 91.210.17.125: set IPv6 to 2001:7f8:14::d6:2 (now empty).
- In the entry with IPv4 91.210.17.25: set IPv6 to 2001:7f8:14::d6:1 (now empty).
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 IPv6 address missing from PeeringDB none 2001:7f8:91::72:1 2001:7f8:91::72:2 - In the entry with IPv4 194.30.187.124: set IPv6 to 2001:7f8:91::72:2 (now empty).
- In the entry with IPv4 194.30.187.24: set IPv6 to 2001:7f8:91::72:1 (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 OTT UKRAINE has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 193.169.199.87 IPv6 – Speed 200000 Mbps (200G)
From ixreport.com/net/204384/: 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.