ixreport

Runet Business Systems

AS60544 · RBS-DSP

LLC Runet Business Systems

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

Tools: Where can I peer with Runet Business Systems? · Where should Runet Business Systems peer next? · Compare Runet Business Systems with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in Runet Business Systems's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Runet Business Systems'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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs200M200G
    • In the entry with IPv4 80.81.192.145: set Speed to 200000 (200G) (now 200).
  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:20:101::208:197 2001:7f8:20:101::210:662001:7f8:20:101::208:197
    • In the entry with IPv4 195.208.210.66: set IPv6 to (empty) (now 2001:7f8:20:101::210:66).

    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

012Oct 3, 2026Nov 19, 20262
Show as a table
DateExchanges
Nov 19, 20262
Nov 18, 20262
Nov 17, 20262
Nov 16, 20262
Nov 15, 20262
Nov 14, 20262
Nov 13, 20262
Nov 12, 20262
Nov 11, 20262
Nov 10, 20262
Nov 9, 20262
Nov 8, 20262
Nov 7, 20262
Nov 6, 20262
Nov 5, 20262
Nov 4, 20262
Nov 3, 20262
Nov 2, 20262
Nov 1, 20262
Oct 31, 20262
Oct 30, 20262
Oct 29, 20262
Oct 28, 20262
Oct 27, 20262
Oct 26, 20262
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 Runet Business Systems'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 2.2G across 2 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.192.145 2001:7f8::ec80:0:1 200M Up, 0 routes Both Speed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.208.197
195.208.210.66
2001:7f8:20:101::208:197
2001:7f8:20:101::210:66
2 × 1G Yes Both IPv6 not in export

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

These exchanges have a switch in a facility where Runet Business Systems lists itself in PeeringDB, but don't have Runet Business Systems 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.

Netherlands GNM-IXAmsterdam, Netherlands 741 Moscow M9; DataSpace Moscow
Russia PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; DataSpace Moscow
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 1 of 9
Russia DataSpace MoscowMoscow 1 of 3
Russia IT-Park DC KazanKazan No exchange