ixreport

Rostelecom

AS12389 · RT

ROSTELECOM

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Rostelecom'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 (9)

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

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export
    IPv4194.85.107.74
    IPv62001:7f8:20:301::107:74
    SpeedNot published
    RS peerNo

    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

    3 connections, so 3 entries:

    IPv4195.208.208.238
    IPv62001:7f8:20:101::208:238
    SpeedNot published
    RS peerYes
    IPv4195.208.209.65
    IPv62001:7f8:20:101::209:65
    SpeedNot published
    RS peerYes
    IPv4195.208.208.183
    IPv62001:7f8:20:101::208:183
    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 MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223From its IX-F export
    IPv4193.232.87.43
    IPv62001:7f8:20:401::87:43
    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.

  4. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380From its IX-F export
    IPv4193.232.140.42
    IPv62001:7f8:20:501::140:42
    SpeedNot published
    RS peerNo

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

  5. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    6 connections, so 6 entries:

    IPv4194.226.102.135
    IPv62001:7f8:20:202::102:135
    SpeedNot published
    RS peerYes
    IPv4194.226.102.140
    IPv62001:7f8:20:202::102:140
    SpeedNot published
    RS peerYes
    IPv4194.226.100.140
    IPv62001:7f8:20:201::100:140
    SpeedNot published
    RS peerYes
    IPv4194.226.100.135
    IPv62001:7f8:20:201::100:135
    SpeedNot published
    RS peerYes
    IPv4194.226.100.93
    IPv62001:7f8:20:201::100:93
    SpeedNot published
    RS peerYes
    IPv4194.226.102.93
    IPv62001:7f8:20:202::102:93
    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.

  6. Russia MSK-IX Samara Samara, Russia · PeeringDB 379From its IX-F export
    IPv4193.232.135.47
    IPv62001:7f8:20:601::135:47
    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.

  7. Russia MSK-IX Vladivostok Vladivostok, Russia · PeeringDB 378From its IX-F export
    IPv4193.232.136.46
    IPv62001:7f8:20:701::136:46
    SpeedNot published
    RS peerNo

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

  8. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.182
    IPv62001:7f8:d:fb::182
    SpeedNot published
    RS peerNo
  9. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.182
    IPv62001:7f8:d:fc::182
    SpeedNot published
    RS peerNo

Correct these entries (2)

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.225.153 178.18.225.220 178.18.236.63178.18.224.129 178.18.225.153 178.18.225.220 178.18.225.239 178.18.236.63
    IPv6 address missing from PeeringDB2a03:5f80:4::225:153 2a03:5f80:4::225:220 2a03:5f80:4:2::236:632a03:5f80:4::224:129 2a03:5f80:4::225:153 2a03:5f80:4::225:220 2a03:5f80:4::225:239 2a03:5f80:4:2::236:63
    Port speed differs2 × 200G + 100G400G + 2 × 200G + 2 × 100G
    • Add an entry: IPv4 178.18.225.239, IPv6 2a03:5f80:4::225:239, speed 100000 (100G), RS peer no.
    • Add an entry: IPv4 178.18.224.129, IPv6 2a03:5f80:4::224:129, speed 400000 (400G), 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.

  2. ProblemPeeringDB hasThe export has
    IPv4 address differs194.68.128.27194.68.128.182
    IPv6 address differs2001:7f8:d:fe::272001:7f8:d:fe::182
    • In the entry with IPv4 194.68.128.27: set IPv4 to 194.68.128.182 (now 194.68.128.27); set IPv6 to 2001:7f8:d:fe::182 (now 2001:7f8:d:fe::27).

Check these entries (1)

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126Not on its website members list
    IPv4101.203.88.213
    IPv62001:de8:c::1:2389:1
    Speed100000 Mbps (100G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges over time

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

Map

Where Rostelecom'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 1.8T, at the 10 of 19 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Hong Kong BBIX Hong Kong Hong Kong, Hong Kong 103.203.158.122 2403:c780:b800:bb00:0:1:2389:1 20G PeeringDB
Japan BBIX Tokyo Tokyo, Japan 101.203.88.213 2001:de8:c::1:2389:1 100G PeeringDB only
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.194.31 2001:7f8::3065:0:1 700G Down Both
Hong Kong Equinix Hong Kong Hong Kong, Hong Kong 36.255.56.185 2001:de8:7::1:2389:1 20G PeeringDB
Japan Equinix Tokyo Tokyo, Japan 203.190.230.145 2001:de8:5::1:2389:1 20G PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.153
178.18.225.220
178.18.236.63
2a03:5f80:4::225:153
2a03:5f80:4::225:220
2a03:5f80:4:2::236:63
2 × 200G + 100G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Japan JPNAP Tokyo Tokyo, Japan 210.173.176.137 2001:7fa:7:1:0:1:2389:1 10G PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.74 2001:7f8:20:301::107:74 Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.208.183
195.208.208.238
195.208.209.65
2001:7f8:20:101::208:183
2001:7f8:20:101::208:238
2001:7f8:20:101::209:65
Yes Not in PeeringDB
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.43 2001:7f8:20:401::87:43 Yes Not in PeeringDB
Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia 193.232.140.42 2001:7f8:20:501::140:42 Not in PeeringDB
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.93
194.226.100.135
194.226.100.140
194.226.102.93
194.226.102.135
194.226.102.140
2001:7f8:20:201::100:93
2001:7f8:20:201::100:135
2001:7f8:20:201::100:140
2001:7f8:20:202::102:93
2001:7f8:20:202::102:135
2001:7f8:20:202::102:140
Yes Not in PeeringDB
Russia MSK-IX Samara Samara, Russia 193.232.135.47 2001:7f8:20:601::135:47 Yes Not in PeeringDB
Russia MSK-IX Vladivostok Vladivostok, Russia 193.232.136.46 2001:7f8:20:701::136:46 Not in PeeringDB
Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden 194.68.128.27 2001:7f8:d:fe::27 100G Both IPv4 differsIPv6 differs
Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden 195.69.119.182 2001:7f8:d:fb::182 Not in PeeringDB
Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden 194.68.123.182 2001:7f8:d:ff::182 100G Both
Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden 195.245.240.182 2001:7f8:d:fc::182 Not in PeeringDB
Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 193.239.118.50 2001:7f8:13::a501:2389:1 200G Yes Both

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

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

Germany KleyReXFrankfurt, Germany 471 ITENOS Frankfurt (FRA1)
Hong Kong HKIXHong Kong, Hong Kong 300 MEGA-i (iAdvantage Hong Kong)
Poland 1-IX EUNew-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland 283 Equinix HK1 - Hong Kong
Japan JPIX TOKYOTokyo, Japan 275 NTT DATA Otemachi Bldg
Bulgaria NetIXSofia, Bulgaria 204 Equinix SK1 - Stockholm, Bromma; Equinix HK1 - Hong Kong; MEGA-i (iAdvantage Hong Kong) and 1 more
Netherlands Global-IXAmsterdam, Netherlands 138 Equinix SK1 - Stockholm, Bromma
Germany ERA-IX FrankfurtFrankfurt, Germany 85 ITENOS Frankfurt (FRA1)
Sweden STHIX - StockholmStockholm, Sweden 84 Equinix SK1 - Stockholm, Bromma
Sweden SONIX StockholmStockholm, Sweden 81 Equinix SK1 - Stockholm, Bromma
Lithuania BALT-IXVilnius, Lithuania 77 Equinix SK1 - Stockholm, Bromma
Sweden SOLIX MTU1500Stockholm, Sweden 58 Equinix SK1 - Stockholm, Bromma
Hong Kong Hong Kong Global Internet ExchangeHong Kong, Hong Kong 33 Equinix HK1 - Hong Kong
Japan Japan Community IXJapan, Japan 32 NTT DATA Otemachi Bldg
Japan DIX-IETokyo, Japan 22 NTT DATA Otemachi Bldg
Hong Kong IAIXHong Kong, Hong Kong 20 MEGA-i (iAdvantage Hong Kong)
Sweden SOLIX MTU4470Stockholm, Sweden 18 Equinix SK1 - Stockholm, Bromma
Sweden Equinix StockholmStockholm, Sweden 17 Equinix SK1 - Stockholm, Bromma
Japan Japan Community IX - INIXPJapan, Japan 15 NTT DATA Otemachi Bldg
Germany MAINPORT Peer-ExchangeFrankfurt am Main, Germany 14 ITENOS Frankfurt (FRA1)
Sweden KeFF-IXStockholm, Gothenburg, Malmö, Amsterdam, Sweden 11 Equinix SK1 - Stockholm, Bromma
United States Global Peer ExchangeWashington, United States 6 Equinix HK1 - Hong Kong
Facilities (5)

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

Sweden Equinix SK1 - Stockholm, BrommaStockholm 5 of 14
Hong Kong Equinix HK1 - Hong KongTsuen Wan 2 of 6
Japan NTT DATA Otemachi BldgTokyo 1 of 6
Germany ITENOS Frankfurt (FRA1)Frankfurt 2 of 5
Hong Kong MEGA-i (iAdvantage Hong Kong)Hong Kong 1 of 4

Recent changes Search them

  • Nov 18, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Nov 18, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Nov 17, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Nov 17, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Nov 9, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Nov 9, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Nov 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Nov 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Nov 5, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Nov 5, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Nov 5, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Nov 5, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Nov 2, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Nov 2, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Nov 2, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Nov 2, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Oct 29, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Oct 29, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Oct 29, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Oct 29, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Oct 21, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Oct 21, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Oct 21, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Oct 21, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Oct 20, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Oct 20, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Oct 19, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Oct 19, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Oct 10, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Oct 10, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Oct 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Oct 9, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok
  • Oct 8, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Novosibirsk
  • Oct 8, 2026 [IXF] AS12389 Rostelecom added to MSK-IX Vladivostok
  • Oct 8, 2026 [IXF] AS12389 Rostelecom left MSK-IX Novosibirsk
  • Oct 8, 2026 [IXF] AS12389 Rostelecom left MSK-IX Vladivostok