ixreport

Fortex-Telecom

AS48166 · Fortex

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list

Nothing to fix: Fortex-Telecom's PeeringDB record matches the member lists of the 2 exchanges we could compare (the others publish no list we could read).

Exchanges over time

02468Oct 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, 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 Fortex-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 100G across 5 exchanges.

Russia CLOUD-IX MSK Moscow, Russia 31.28.19.139 2a00:13c0:3:1::1f1c:138b 10G Yes PeeringDB
Russia Eurasia Peering IX Moscow, Russia 185.232.60.128 2a0d:e180::60:128 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.128 2a03:5f80:4::226:128 20G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.209.61 2001:7f8:20:101::209:61 20G Yes Both
Russia W-IX Moscow, Russia 193.106.112.218 40G Yes PeeringDB

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

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

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 SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 5 of 9
Russia Moscow TehnoGorodMoscow 3 of 3
Russia Moscow M10Moscow 1 of 1

Recent changes Search them

  • Oct 17, 2026 [PDB] AS48166 Fortex-Telecom now in PeeringDB at GNM-IX
  • Oct 16, 2026 [PDB] AS48166 Fortex-Telecom no longer in PeeringDB at GNM-IX (still on its IX-F list)
  • Oct 16, 2026 [PDB] AS48166 Fortex-Telecom left PITER-IX Saint-Petersburg
  • Oct 16, 2026 [PDB] AS48166 Fortex-Telecom left PITER-IX Tallinn
  • Oct 16, 2026 [PDB] AS48166 Fortex-Telecom left PITER-IX Helsinki