Telecom-Birzha
AS199599 · CIREX (Биржа цепей)
Telecom-Birzha LLC
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.
-
IPv4 80.81.194.178 IPv6 2001:7f8::3:baf:0:1 Speed 400000 Mbps (400G) RS peer Yes -
2 connections, so 2 entries:
IPv4 178.18.224.113 IPv6 2a03:5f80:4::224:113 Speed 100000 Mbps (100G) RS peer Yes IPv4 178.18.224.47 IPv6 2a03:5f80:4::224:47 Speed 100000 Mbps (100G) 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.
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.208.210.85 195.208.209.85 195.208.210.85 IPv6 address missing from PeeringDB 2001:7f8:20:101::210:85 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 8 |
| Nov 18, 2026 | 8 |
| Nov 17, 2026 | 8 |
| Nov 16, 2026 | 8 |
| Nov 15, 2026 | 8 |
| Nov 14, 2026 | 8 |
| Nov 13, 2026 | 8 |
| Nov 12, 2026 | 8 |
| Nov 11, 2026 | 8 |
| Nov 10, 2026 | 8 |
| Nov 9, 2026 | 8 |
| Nov 8, 2026 | 8 |
| Nov 7, 2026 | 8 |
| Nov 6, 2026 | 8 |
| Nov 5, 2026 | 8 |
| Nov 4, 2026 | 8 |
| Nov 3, 2026 | 8 |
| Nov 2, 2026 | 8 |
| Nov 1, 2026 | 8 |
| Oct 31, 2026 | 8 |
| Oct 30, 2026 | 8 |
| Oct 29, 2026 | 8 |
| Oct 28, 2026 | 8 |
| Oct 27, 2026 | 8 |
| Oct 26, 2026 | 8 |
| Oct 25, 2026 | 8 |
| Oct 24, 2026 | 8 |
| Oct 23, 2026 | 8 |
| Oct 22, 2026 | 8 |
| Oct 21, 2026 | 8 |
| Oct 20, 2026 | 8 |
| Oct 19, 2026 | 8 |
| Oct 18, 2026 | 8 |
| Oct 17, 2026 | 8 |
| Oct 16, 2026 | 8 |
| Oct 15, 2026 | 8 |
| Oct 14, 2026 | 8 |
| Oct 13, 2026 | 8 |
| Oct 12, 2026 | 8 |
| Oct 11, 2026 | 8 |
| Oct 10, 2026 | 8 |
| Oct 9, 2026 | 8 |
| Oct 8, 2026 | 8 |
| Oct 7, 2026 | 8 |
| Oct 6, 2026 | 8 |
| Oct 5, 2026 | 8 |
| Oct 4, 2026 | 8 |
| Oct 3, 2026 | 8 |
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.
| DE-CIX Frankfurt Frankfurt, Germany | 400G | Not in PeeringDB | |
| Global-IX Amsterdam, Netherlands | 100G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 100G | Not in PeeringDB | |
| MSK-IX Moscow Moscow, Russia | 200G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| PITER-IX Frankfurt Frankfurt, Germany | 100G | PeeringDB | |
| PITER-IX Helsinki Helsinki, Finland | 100G | PeeringDB | |
| PITER-IX Moscow Moscow, Russia | 100G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 100G | PeeringDB |
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.
| Eurasia Peering IXMoscow, Russia | 136 | |
| W-IXMoscow, Russia | 66 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| Linxdatacenter-IXMoscow, Russia | 5 | |
| ixFabricGlobal, Australia | 2 |
Facilities (8)
The buildings Telecom-Birzha lists in PeeringDB, and how many of the exchanges in each it's on.
| Moscow M9Moscow | 5 of 9 | |
| IXcellerate MOS1Moscow | 4 of 6 | |
| DataLine Moscow 1Dolgoprudny | 2 of 4 | |
| DataLine Moscow 2Balashikha | 1 of 3 | |
| DataSpace MoscowMoscow | 2 of 3 | |
| Linxdatacenter (Moscow)Moscow | 2 of 3 | |
| Moscow M10Moscow | 1 of 1 | |
| 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)