ixreport

Erlang

AS47569 · Erlang

Erlang company Ltd.

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Erlang's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Erlang 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.175
    IPv6–
    Speed10000 Mbps (10G)
  2. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.100.75
    IPv6–
    SpeedNot published
    IPv4194.226.102.75
    IPv6–
    SpeedNot published

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, 20264
Oct 24, 20264
Oct 23, 20264
Oct 22, 20264
Oct 21, 20264
Oct 20, 20264
Oct 19, 20264
Oct 18, 20264
Oct 17, 20264
Oct 16, 20264
Oct 15, 20264
Oct 14, 20264
Oct 13, 20264
Oct 12, 20264
Oct 11, 20264
Oct 10, 20264
Oct 9, 20264
Oct 8, 20264
Oct 7, 20264
Oct 6, 20264
Oct 5, 20264
Oct 4, 20264
Oct 3, 20264

Map

Where Erlang'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 30G, at the 3 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.75 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.210.75 10G Yes PeeringDB only
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.175 10G Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.75
194.226.102.75
Yes PeeringDB only

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

These exchanges have a switch in a facility where Erlang lists itself in PeeringDB, but don't have Erlang 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.

Netherlands GNM-IXAmsterdam, Netherlands 741 Erlang.Ekb.MS145
Russia CLOUD-IX MSKMoscow, Russia 52 Erlang.Ekb.MS145
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Erlang.Ekb.MS145
Russia CLOUD-IX EKTEkaterinburg, Russia 6 Erlang.Ekb.MS145
Facilities (2)

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

Russia Erlang.Ekb.MS145Ekaterinburg 1 of 5
Russia Erlang.Ekb.SH10Ekaterinburg No exchange