ixreport

Sibirskie Seti AS34757

AS34757

Sibirskie Seti Ltd.

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

Tools: Where can I peer with Sibirskie Seti AS34757? · Where should Sibirskie Seti AS34757 peer next? · Compare Sibirskie Seti AS34757 with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Sibirskie Seti AS34757'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 Sibirskie Seti AS34757'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 Sibirskie Seti AS34757's PeeringDB record. Add one entry per connection with these values.

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

    2 connections, so 2 entries:

    IPv4178.18.233.26
    IPv62a03:5f80:4:1::233:26
    Speed20000 Mbps (20G)
    RS peerYes
    IPv4178.18.226.154
    IPv62a03:5f80:4::226:154
    Speed10000 Mbps (10G)
    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 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.

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 Novosibirsk Novosibirsk, Russia · PeeringDB 223
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:401::87:61
    • In the entry with IPv4 193.232.87.61: set IPv6 to 2001:7f8:20:401::87:61 (now empty).

    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, 20262
Oct 24, 20262
Oct 23, 20262
Oct 22, 20262
Oct 21, 20262
Oct 20, 20262
Oct 19, 20262
Oct 18, 20262
Oct 17, 20262
Oct 16, 20262
Oct 15, 20262
Oct 14, 20262
Oct 13, 20262
Oct 12, 20262
Oct 11, 20262
Oct 10, 20262
Oct 9, 20262
Oct 8, 20262
Oct 7, 20262
Oct 6, 20262
Oct 5, 20262
Oct 4, 20262
Oct 3, 20262

Map

Where Sibirskie Seti AS34757'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 50G, 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.226.154
178.18.233.26
2a03:5f80:4::226:154
2a03:5f80:4:1::233:26
20G + 10G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia Website list only
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.61 20G Yes Both IPv6 not in PeeringDB

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

These exchanges have a switch in a facility where Sibirskie Seti AS34757 lists itself in PeeringDB, but don't have Sibirskie Seti AS34757 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 SFO-IXBarnaul, Novosibirsk, Russia 30 Sinar
Facilities (1)

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

Russia SinarNovosibirsk 2 of 3