ixreport

Setel

AS39153 · Almatel

Setel LLC

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

Tools: Where can I peer with Setel? · Where should Setel peer next? · Compare Setel 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 Setel's exchanges publish a member list we could read this time.

Exchanges over time

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

Map

Where Setel'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 370G across 7 exchanges.

Russia DataLine-IX Moscow, Russia 185.1.52.28 10G Yes PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.110 60G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.186 60G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.12.143 60G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.142 60G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.99 60G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.160 60G Yes PeeringDB

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

These exchanges have a switch in a facility where Setel lists itself in PeeringDB, but don't have Setel 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; Linxdatacenter (Moscow); StoreData and 1 more
Russia MSK-IX MoscowMoscow, Russia 638 Moscow M9; Linxdatacenter (Moscow); CSS MPS Moscow and 4 more
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; StoreData
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9; Moscow TehnoGorod; DataLine Moscow 1
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; StoreData; Moscow TehnoGorod and 1 more
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Russia Linxdatacenter-IXMoscow, Russia 5 Linxdatacenter (Moscow)
Facilities (7)

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

Russia Moscow M9Moscow 2 of 9
Russia DataLine Moscow 1Dolgoprudny 0 of 4
Russia StoreDataMoscow 0 of 4
Russia Linxdatacenter (Moscow)Moscow 0 of 3
Russia Moscow TehnoGorodMoscow 0 of 3
Russia CSS MPS MoscowMoscow 0 of 1
Russia Moscow M10Moscow 0 of 1