ixreport

Severen-Telecom

AS24739 · Severen

JSC "Severen-Telecom"

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

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

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Severen-Telecom's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-11-19 12:40 UTC.

Make the changes on Severen-Telecom'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 (1)

On the exchange's own member list, but not in Severen-Telecom's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Exchanges over time

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

Map

Where Severen-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 20G, at the 2 of 3 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Russia CLOUD-IX SPB St. Petersburg, Russia 31.28.18.84 2a00:13c0:3:2::1f1c:1254 10G Yes PeeringDB
Russia MSK-IX Moscow Moscow, Russia Website list only
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.70 10G Yes PeeringDB

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

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

Facilities (7)

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

Russia IVC ORW Saint-PetersburgSt. Petersburg 2 of 10
Russia Bolshaya Morskaya 18St. Petersburg 2 of 9
Russia Raduga-2St. Petersburg 2 of 8
Russia Tsvetochnaya Data CenterSt. Petersburg 2 of 8
Russia RETNNet OV DCSt. Petersburg 0 of 2
Russia XelentSt. Petersburg 1 of 2
Russia Linxdatacenter (Saint-Petersburg)St. Petersburg 0 of 1