ixreport

Sberbank

AS35237 · Sberbank

Sberbank of Russia

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
SelectivePeering policy
5Using the route servers
2To fix in PeeringDB
3Facilities in PeeringDB

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on Sberbank'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 (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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::226:70
    Port speed differs20G100G
    • In the entry with IPv4 178.18.226.70: set IPv6 to 2a03:5f80:4::226:70 (now empty); set Speed to 100000 (100G) (now 20000).

    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 100
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:101::209:221
    • In the entry with IPv4 195.208.209.221: set IPv6 to 2001:7f8:20:101::209:221 (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

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

Map

Where Sberbank'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 90G across 5 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.141 10G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.212 20G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.70 20G Yes Both IPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.209.221 20G Yes Both IPv6 not in PeeringDB
Russia W-IX Moscow, Russia 193.106.113.64 20G Yes PeeringDB

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

These exchanges have a switch in a facility where Sberbank lists itself in PeeringDB, but don't have Sberbank 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 PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 5 of 9
Russia Moscow M10Moscow 1 of 1
Russia Stack.M1Moscow No exchange