ixreport

MiraLogic Telecommunication Systems

AS12668

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

Tools: Where can I peer with MiraLogic Telecommunication Systems? · Where should MiraLogic Telecommunication Systems peer next? · Compare MiraLogic Telecommunication Systems with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in MiraLogic Telecommunication Systems's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-11-19 18:41 UTC.

Make the changes on MiraLogic Telecommunication Systems'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 MiraLogic Telecommunication Systems'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.16
    IPv62a03:5f80:4:1::233:16
    Speed30000 Mbps (30G)
    RS peerYes
    IPv4178.18.225.156
    IPv62a03:5f80:4::225:156
    Speed30000 Mbps (30G)
    RS peerYes

    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 MiraLogic Telecommunication Systems 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.247
    IPv62001:7f8:20:401::87:247
    SpeedNot published
  2. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.100.247
    IPv62001:7f8:20:201::100:247
    SpeedNot published
    IPv4194.226.102.247
    IPv62001:7f8:20:202::102:247
    SpeedNot published

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 MiraLogic Telecommunication Systems'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 1 of 5 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.156
178.18.233.16
2a03:5f80:4::225:156
2a03:5f80:4:1::233:16
30G Yes Not in PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.47 2001:7f8:20:301::107:47 Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.210.247 2001:7f8:20:101::210:247 Yes PeeringDB only
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.247 2001:7f8:20:401::87:247 Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.247
194.226.102.247
2001:7f8:20:201::100:247
2001:7f8:20:202::102:247
Yes PeeringDB only

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

These exchanges have a switch in a facility where MiraLogic Telecommunication Systems lists itself in PeeringDB, but don't have MiraLogic Telecommunication Systems 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 (2)

The buildings MiraLogic Telecommunication Systems 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