ixreport

JSC SEVEREN-TELECOM

AS35000 · JSC SEVEREN-TELECOM

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
SelectivePeering policy
6Using the route servers
4To fix in PeeringDB
13Facilities in PeeringDB

Tools: Where can I peer with JSC SEVEREN-TELECOM? · Where should JSC SEVEREN-TELECOM peer next? · Compare JSC SEVEREN-TELECOM with another network

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

PeeringDB fix list Printable page · CSV

4 things to fix in JSC SEVEREN-TELECOM's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on JSC 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.

Correct these entries (4)

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.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs10G3G
    • In the entry with IPv4 80.249.209.5: set Speed to 3000 (3G) (now 10000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.224.36 178.18.224.37178.18.224.36 178.18.224.37 178.18.225.37
    IPv6 address missing from PeeringDB2a03:5f80:4::224:36 2a03:5f80:4::224:372a03:5f80:4::224:36 2a03:5f80:4::224:37 2a03:5f80:4::225:37
    Port speed differs2 × 20G3 × 10G
    • In the entry with IPv4 178.18.224.36: set Speed to 10000 (10G) (now 20000).
    • In the entry with IPv4 178.18.224.37: set Speed to 10000 (10G) (now 20000).
    • Add an entry: IPv4 178.18.225.37, IPv6 2a03:5f80:4::225:37, speed 10000 (10G), 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.

  3. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.208.119195.208.208.119 195.208.208.165
    IPv6 address missing from PeeringDB2001:7f8:20:101::208:1192001:7f8:20:101::208:119 2001:7f8:20:101::208:165
    • Add an entry: IPv4 195.208.208.165, IPv6 2001:7f8:20:101::208:165, 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.

  4. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.226.102.78194.226.100.78 194.226.102.78
    IPv6 address missing from PeeringDB2001:7f8:20:202::102:782001:7f8:20:201::100:78 2001:7f8:20:202::102:78
    • Add an entry: IPv4 194.226.100.78, IPv6 2001:7f8:20:201::100:78, 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

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

Map

Where JSC 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 110G across 6 exchanges.

Netherlands AMS-IX Amsterdam, Netherlands 80.249.209.5 2001:7f8:1::a503:5000:1 10G 336 routes Both Speed differs
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.36
178.18.224.37
2a03:5f80:4::224:36
2a03:5f80:4::224:37
2 × 20G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.208.119 2001:7f8:20:101::208:119 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.102.78 2001:7f8:20:202::102:78 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.7 10G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.113.71 2a00:1b30::a71 30G Yes PeeringDB

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

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

Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9; Bolshaya Morskaya 18; IVC ORW Saint-Petersburg and 3 more
Bulgaria NetIXSofia, Bulgaria 204 IVC ORW Saint-Petersburg
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; Bolshaya Morskaya 18; IVC ORW Saint-Petersburg and 2 more
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; Bolshaya Morskaya 18; IVC ORW Saint-Petersburg and 4 more
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Russia CLOUD-IX SPBSt. Petersburg, Russia 25 Bolshaya Morskaya 18; IVC ORW Saint-Petersburg; Tsvetochnaya Data Center and 3 more
Russia PIRIXSt.Petersburg, Russia 6 Bolshaya Morskaya 18; IVC ORW Saint-Petersburg; Tsvetochnaya Data Center and 4 more
Facilities (13)

The buildings JSC SEVEREN-TELECOM lists in PeeringDB, and how many of the exchanges in each it's on.

Russia IVC ORW Saint-PetersburgSt. Petersburg 4 of 10
Russia Bolshaya Morskaya 18St. Petersburg 4 of 9
Russia Moscow M9Moscow 4 of 9
Russia Raduga-2St. Petersburg 3 of 8
Russia Tsvetochnaya Data CenterSt. Petersburg 3 of 8
Russia Miran-1Санкт-Петербург 1 of 5
Russia RETNNet OV DCSt. Petersburg 1 of 2
Russia XelentSt. Petersburg 0 of 2
Russia Linxdatacenter (Saint-Petersburg)St. Petersburg 1 of 1
Russia Miran-2St. Petersburg 0 of 1
Russia Prometey Ltd SPB MM11St. Petersburg 1 of 1
Russia COD BM-18St.Petersburg No exchange
Russia Prometey Ltd SPB A6St.Petersburg No exchange