ixreport

Key Telecom

AS49814

4Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
3Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Key Telecom? · Where should Key Telecom peer next? · Compare Key Telecom with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Key Telecom's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-11-19 18:41 UTC.

Make the changes on Key Telecom'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 (2)

On the exchange's own member list, but not in Key Telecom's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.226.77
    IPv62a03:5f80:4::226:77
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.226.83
    IPv62a03:5f80:4::226:83
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Key Telecom's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 50G, at the 3 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.77
178.18.226.83
2a03:5f80:4::226:77
2a03:5f80:4::226:83
10G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia Website list only
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.105
193.232.87.110
2001:7f8:20:401::87:105
2001:7f8:20:401::87:110
2 × 10G Yes Both
Russia SFO-IX Barnaul, Novosibirsk, Russia 91.221.180.78
91.221.180.79
2a0b:9fc0:1:0:3:9701:180:78
2a0b:9fc0:1:0:3:9701:180:79
2 × 10G Yes PeeringDB

Key Telecom lists no facilities in PeeringDB.