ixreport

Mail.Ru Group

AS47764 · VK

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

Tools: Where can I peer with Mail.Ru Group? · Where should Mail.Ru Group peer next? · Compare Mail.Ru Group with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Mail.Ru Group's PeeringDB record, from what its exchanges publish: 3 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Mail.Ru Group'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 (3)

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

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

    3 connections, so 3 entries:

    IPv4178.18.225.32
    IPv62a03:5f80:4::225:32
    Speed1300000 Mbps (1.3T)
    RS peerYes
    IPv4178.18.226.150
    IPv62a03:5f80:4::226:150
    Speed900000 Mbps (900G)
    RS peerYes
    IPv4178.18.226.116
    IPv62a03:5f80:4::226:116
    Speed800000 Mbps (800G)
    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

    5 connections, so 5 entries:

    IPv4195.208.209.83
    IPv62001:7f8:20:101::209:83
    SpeedNot published
    RS peerYes
    IPv4195.208.210.12
    IPv62001:7f8:20:101::210:12
    SpeedNot published
    RS peerYes
    IPv4195.208.209.218
    IPv62001:7f8:20:101::209:218
    SpeedNot published
    RS peerYes
    IPv4195.208.209.250
    IPv62001:7f8:20:101::209:250
    SpeedNot published
    RS peerYes
    IPv4195.208.210.91
    IPv62001:7f8:20:101::210:91
    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. Uzbekistan SNS-IX Tashkent, Uzbekistan · PeeringDB 2836From 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

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 Mail.Ru Group'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 3T, 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.32
178.18.226.116
178.18.226.150
178.18.230.126
2a03:5f80:4::225:32
2a03:5f80:4::226:116
2a03:5f80:4::226:150
2a03:5f80:7::230:126
1.3T + 900G + 800G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 194.226.100.87
194.226.100.191
194.226.100.250
194.226.101.11
194.226.101.83
194.226.102.87
194.226.102.191
194.226.102.250
194.226.103.11
194.226.103.83
195.208.209.83
195.208.209.218
195.208.209.250
195.208.210.12
195.208.210.91
2001:7f8:20:101::209:83
2001:7f8:20:101::209:218
2001:7f8:20:101::209:250
2001:7f8:20:101::210:12
2001:7f8:20:101::210:91
2001:7f8:20:201::100:87
2001:7f8:20:201::100:191
2001:7f8:20:201::100:250
2001:7f8:20:201::101:11
2001:7f8:20:201::101:83
2001:7f8:20:202::102:87
2001:7f8:20:202::102:191
2001:7f8:20:202::102:250
2001:7f8:20:202::103:11
2001:7f8:20:202::103:83
Yes Not in PeeringDB
Uzbekistan SNS-IX Tashkent, Uzbekistan Not in PeeringDB

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

These exchanges have a switch in a facility where Mail.Ru Group lists itself in PeeringDB, but don't have Mail.Ru Group 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 PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9; DataLine Moscow 1
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; DataLine Moscow 1; DataLine Moscow 2
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Australia ixFabricGlobal, Australia 2 DataLine Moscow 2
Facilities (4)

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

Russia Moscow M9Moscow 2 of 9
Russia DataLine Moscow 1Dolgoprudny 2 of 4
Russia DataLine Moscow 2Balashikha 1 of 3
Russia M100 datacenter Moscow, Varshavskoe 125Moscow 1 of 1