ixreport

BAIKAL-IX IP-TRANSIT

AS57277 · Байкал-IX

BAIKAL-IX

11Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
11Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with BAIKAL-IX IP-TRANSIT? · Where should BAIKAL-IX IP-TRANSIT peer next? · Compare BAIKAL-IX IP-TRANSIT with another network

This network elsewhere: its registry history on RIR Tracker

PeeringDB fix list Printable page · CSV

One thing to fix in BAIKAL-IX IP-TRANSIT's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on BAIKAL-IX IP-TRANSIT's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs40G10G
    • In the entry with IPv4 178.18.224.107: set Speed to 10000 (10G) (now 40000).

    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

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

Map

Where BAIKAL-IX IP-TRANSIT'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 490G across 11 exchanges.

Russia BAIKAL-IX Irkutsk, Russia 185.1.76.200 200G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.253 40G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.107 2a03:5f80:4::224:107 40G Yes Both Speed differs
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.40 2001:7f8:20:301::107:40 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.210.6 2001:7f8:20:101::210:6 40G Yes Both
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.41 2001:7f8:20:401::87:41 10G Yes Both
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.109 40G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.170 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.238 40G Yes PeeringDB
Russia SFO-IX Barnaul, Novosibirsk, Russia 91.221.180.103 20G Yes PeeringDB
Russia Sibir-IX Krasnoyarsk, Russia 185.1.81.7 10G Yes PeeringDB

BAIKAL-IX IP-TRANSIT lists no facilities in PeeringDB.