ixreport

evo73_MSK

AS50716

3Exchanges
3On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
2Using the route servers
4To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

AS50716 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (3)

On the exchange's own member list, but not in evo73_MSK'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.225.252
    IPv62a03:5f80:4::225:252
    Speed30000 Mbps (30G)
    RS peerYes
    IPv4178.18.225.36
    IPv62a03:5f80:4::225:36
    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.

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

    2 connections, so 2 entries:

    IPv4195.208.211.33
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4195.208.211.23
    IPv62001:7f8:20:101::211:23
    SpeedNot published
    RS peerYes

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

  3. Russia ULN-IX Ulyanovsk, Russia · PeeringDB 340From its IX-F export
    IPv4185.1.19.30
    IPv62001:7f8:7d::c61c:1
    SpeedNot published
    RS peerNot published

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 Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB195.208.211.23 is AS199651 CLOUDTRANSIT195.208.211.23
    Address belongs to another network in PeeringDB2001:7f8:20:101::211:23 is AS199651 CLOUDTRANSIT2001:7f8:20:101::211:23

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
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 evo73_MSK'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 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.36
178.18.225.252
2a03:5f80:4::225:36
2a03:5f80:4::225:252
30G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.211.23
195.208.211.33
2001:7f8:20:101::211:23 Yes Not in PeeringDB Address taken
Russia ULN-IX Ulyanovsk, Russia 185.1.19.30 2001:7f8:7d::c61c:1 Not in PeeringDB