K Telecom Ldt.: PeeringDB fix list
AS48642 · peeringdb.com/net/8926
3 things to fix in K Telecom Ldt.'s PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-10-08 20:58 UTC.
Make the changes on K Telecom Ldt.'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 (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 Port speed differs 20G + 11G + 8G 40G + 20G - In the entry with IPv4 178.18.225.13: set Speed to 40000 (40G) (now 20000).
- In the entry with IPv4 178.18.225.238: set Speed to 20000 (20G) (now 8000).
- In the entry with IPv4 178.18.233.24: set Speed to 20000 (20G) (now 11000).
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 (2)
In PeeringDB, but on none of the exchange's own lists. If K Telecom Ldt. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.208.210.234 IPv6 2001:7f8:20:101::210:234 Speed 10000 Mbps (10G) -
IPv4 194.226.100.234 IPv6 2001:7f8:20:201::100:234 Speed 10000 Mbps (10G) IPv4 194.226.102.234 IPv6 2001:7f8:20:202::102:234 Speed 10000 Mbps (10G)
From ixreport.com/net/48642/: 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.