KTM Telekom: PeeringDB fix list
AS62201 · peeringdb.com/net/12406
2 things to fix in KTM Telekom's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on KTM Telekom'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 178.216.41.39 178.216.40.117 178.216.41.39 IPv6 address missing from PeeringDB 2001:7f8:5b::294 2001:7f8:5b::165 2001:7f8:5b::294 Port speed differs 10G 2 × 10G - Add an entry: IPv4 178.216.40.117, IPv6 2001:7f8:5b::165, speed 10000 (10G), 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 89.46.145.181 89.46.144.232 89.46.145.181 IPv6 address missing from PeeringDB 2001:678:3ac::557 2001:678:3ac::485 2001:678:3ac::557 Port speed differs 10G 2 × 10G - Add an entry: IPv4 89.46.144.232, IPv6 2001:678:3ac::485, speed 10000 (10G), 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/62201/: 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.