ixreport

Intersvyaz

AS8369 · IS

Intersvyaz-2 JSC

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Intersvyaz'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 (2)

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

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

    6 connections, so 6 entries:

    IPv4178.18.224.180
    IPv62a03:5f80:4::224:180
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.225.43
    IPv62a03:5f80:4::225:43
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.158
    IPv62a03:5f80:4::226:158
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.62
    IPv62a03:5f80:4::226:62
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.92
    IPv62a03:5f80:4::226:92
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.226.95
    IPv62a03:5f80:4::226:95
    Speed100000 Mbps (100G)
    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 Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export

    2 connections, so 2 entries:

    IPv4194.85.107.67
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4194.85.107.78
    IPv6–
    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.

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
    IPv4 address missing from PeeringDB195.208.208.26 195.208.208.228195.208.208.26 195.208.208.228 195.208.210.124 195.208.210.138
    • Add an entry: IPv4 195.208.210.124, IPv6 –, RS peer yes.
    • Add an entry: IPv4 195.208.210.138, IPv6 –, 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.

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 Intersvyaz'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 220G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.180
178.18.225.43
178.18.226.62
178.18.226.92
178.18.226.95
178.18.226.158
2a03:5f80:4::224:180
2a03:5f80:4::225:43
2a03:5f80:4::226:62
2a03:5f80:4::226:92
2a03:5f80:4::226:95
2a03:5f80:4::226:158
100G Yes Not in PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.67
194.85.107.78
Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.208.26
195.208.208.228
2001:7f8:20:101::208:26
2001:7f8:20:101::208:228
2 × 60G Yes Both IPv4 not in PeeringDB

Intersvyaz lists no facilities in PeeringDB.