ixreport

Telecom-Birzha

AS199599 · CIREX (Биржа цепей)

Telecom-Birzha LLC

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

Tools: Where can I peer with Telecom-Birzha? · Where should Telecom-Birzha peer next? · Compare Telecom-Birzha with another network

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

PeeringDB fix list Printable page · CSV

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

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31From its IX-F export and website members list
    IPv480.81.194.178
    IPv62001:7f8::3:baf:0:1
    Speed400000 Mbps (400G)
    RS peerYes
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.224.113
    IPv62a03:5f80:4::224:113
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.224.47
    IPv62a03:5f80:4::224:47
    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.

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.210.85195.208.209.85 195.208.210.85
    IPv6 address missing from PeeringDB2001:7f8:20:101::210:852001:7f8:20:101::209:85 2001:7f8:20:101::210:85
    • Add an entry: IPv4 195.208.209.85, IPv6 2001:7f8:20:101::209:85, 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

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

Map

Where Telecom-Birzha'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 1.2T across 8 exchanges.

Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.194.178 2001:7f8::3:baf:0:1 400G Down Not in PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.34 100G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.47
178.18.224.113
2a03:5f80:4::224:47
2a03:5f80:4::224:113
100G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.210.85 2001:7f8:20:101::210:85 200G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.187.59 100G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.182 100G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.21 100G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.25 100G Yes PeeringDB

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

These exchanges have a switch in a facility where Telecom-Birzha lists itself in PeeringDB, but don't have Telecom-Birzha 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 Eurasia Peering IXMoscow, Russia 136 Moscow M9; IXcellerate MOS1
Russia W-IXMoscow, Russia 66 Moscow M9; DataLine Moscow 1
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; DataLine Moscow 1; DataLine Moscow 2 and 2 more
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Russia Linxdatacenter-IXMoscow, Russia 5 Linxdatacenter (Moscow)
Australia ixFabricGlobal, Australia 2 DataLine Moscow 2
Facilities (8)

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

Russia Moscow M9Moscow 5 of 9
Russia IXcellerate MOS1Moscow 4 of 6
Russia DataLine Moscow 1Dolgoprudny 2 of 4
Russia DataLine Moscow 2Balashikha 1 of 3
Russia DataSpace MoscowMoscow 2 of 3
Russia Linxdatacenter (Moscow)Moscow 2 of 3
Russia Moscow M10Moscow 1 of 1
Russia Stack.M1Moscow No exchange

Recent changes Search them

  • Oct 22, 2026 [IXF] AS199599 Telecom-Birzha now on MSK-IX Moscow's IX-F list
  • Oct 21, 2026 [IXF] AS199599 Telecom-Birzha dropped from MSK-IX Moscow's IX-F list (still in PeeringDB)