ixreport

Gerkon

AS42498 · Gerkon

Gerkon LTD

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

4 things to fix in Gerkon's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 2 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Gerkon'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 Gerkon'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.233.20
    IPv62a03:5f80:4:1::233:20
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.227.65
    IPv62a03:5f80:4::227:65
    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.

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.

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.85.107.36194.85.107.36 194.85.107.66
    • Add an entry: IPv4 194.85.107.66, IPv6 –, 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.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Gerkon has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223Not on its IX-F export
    IPv4193.232.87.136
    IPv6–
    Speed10000 Mbps (10G)
  2. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.100.136
    IPv6–
    Speed10000 Mbps (10G)
    IPv4194.226.102.136
    IPv6–
    Speed10000 Mbps (10G)

Exchanges over time

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

Map

Where Gerkon'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 60G across 5 exchanges.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.65
178.18.233.20
2a03:5f80:4::227:65
2a03:5f80:4:1::233:20
10G Yes Not in PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.36 10G Yes Both IPv4 not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.210.36 10G Yes PeeringDB only
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.136 10G Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.136
194.226.102.136
2 × 10G Yes PeeringDB only

Exchanges in its buildings that it isn't on (3)

These exchanges have a switch in a facility where Gerkon lists itself in PeeringDB, but don't have Gerkon as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Russia CLOUD-IX MSKMoscow, Russia 52 EKB, Uralcod; Erlang.Ekb.MS145
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 EKB, Uralcod; Erlang.Ekb.MS145
Russia CLOUD-IX EKTEkaterinburg, Russia 6 EKB, Uralcod; Erlang.Ekb.MS145
Facilities (3)

The buildings Gerkon lists in PeeringDB, and how many of the exchanges in each it's on.

Russia EKB, UralcodEkaterinburg 2 of 5
Russia Erlang.Ekb.MS145Ekaterinburg 2 of 5
Russia Erlang.Ekb.SH10Ekaterinburg No exchange