ixreport

Magistral_Telecom

AS205553

LTD Magistral_Telecom

5Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
5Using the route servers
1Facility in PeeringDB

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

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

PeeringDB fix list

Nothing to compare: none of Magistral_Telecom's exchanges publish a member list we could read this time.

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 Magistral_Telecom'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 across 5 exchanges.

Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.45 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.138 10G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.178 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.29 10G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.146 10G Yes PeeringDB

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

These exchanges have a switch in a facility where Magistral_Telecom lists itself in PeeringDB, but don't have Magistral_Telecom 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 Raduga-2
Russia PITER-IX MoscowMoscow, Russia 243 Raduga-2
Netherlands Global-IXAmsterdam, Netherlands 138 Raduga-2
Russia MSK-IX Saint-PetersburgSt.Petersburg, Russia 71 Raduga-2
Russia CLOUD-IX MSKMoscow, Russia 52 Raduga-2
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Raduga-2
Russia PIRIXSt.Petersburg, Russia 6 Raduga-2
Facilities (1)

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

Russia Raduga-2St. Petersburg 1 of 8