ixreport

Rostelecom: PeeringDB fix list

AS12389 · peeringdb.com/net/2281

PeeringDB

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-10-08 22:13 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

    3 connections, so 3 entries:

    IPv4195.208.209.65
    IPv62001:7f8:20:101::209:65
    SpeedNot published
    RS peerYes
    IPv4195.208.208.238
    IPv62001:7f8:20:101::208:238
    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.100.135
    IPv62001:7f8:20:201::100:135
    SpeedNot published
    RS peerYes
    IPv4194.226.102.93
    IPv62001:7f8:20:202::102:93
    SpeedNot published
    RS peerYes
    IPv4194.226.102.135
    IPv62001:7f8:20:202::102:135
    SpeedNot published
    RS peerYes
    IPv4194.226.100.140
    IPv62001:7f8:20:201::100:140
    SpeedNot published
    RS peerYes
    IPv4194.226.100.93
    IPv62001:7f8:20:201::100:93
    SpeedNot published
    RS peerYes
    IPv4194.226.102.140
    IPv62001:7f8:20:202::102:140
    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 + 3 × 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. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    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.

From ixreport.com/net/12389/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.