JSC SEVEREN-TELECOM
AS35000 · JSC SEVEREN-TELECOM
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.
-
Problem PeeringDB has The export has Port speed differs 10G 3G - 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.224.36 178.18.224.37 178.18.224.36 178.18.224.37 178.18.225.37 IPv6 address missing from PeeringDB 2a03:5f80:4::224:36 2a03:5f80:4::224:37 2a03:5f80:4::224:36 2a03:5f80:4::224:37 2a03:5f80:4::225:37 Port speed differs 2 × 20G 3 × 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 195.208.208.119 195.208.208.119 195.208.208.165 IPv6 address missing from PeeringDB 2001:7f8:20:101::208:119 2001: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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 194.226.102.78 194.226.100.78 194.226.102.78 IPv6 address missing from PeeringDB 2001:7f8:20:202::102:78 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
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.
| AMS-IX Amsterdam, Netherlands | 10G | Both Speed differs | |
| GNM-IX Amsterdam, Netherlands | 2 × 20G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MSK-IX Moscow Moscow, Russia | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 10G | PeeringDB | |
| W-IX Moscow, Russia | 30G | PeeringDB |
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.
| PITER-IX MoscowMoscow, Russia | 243 | |
| NetIXSofia, Bulgaria | 204 | |
| Global-IXAmsterdam, Netherlands | 138 | |
| Eurasia Peering IXMoscow, Russia | 136 | |
| CLOUD-IX MSKMoscow, Russia | 52 | |
| SFO-IXBarnaul, Novosibirsk, Russia | 30 | |
| CLOUD-IX SPBSt. Petersburg, Russia | 25 | |
| PIRIXSt.Petersburg, Russia | 6 |
Facilities (13)
The buildings JSC SEVEREN-TELECOM lists in PeeringDB, and how many of the exchanges in each it's on.
| IVC ORW Saint-PetersburgSt. Petersburg | 4 of 10 | |
| Bolshaya Morskaya 18St. Petersburg | 4 of 9 | |
| Moscow M9Moscow | 4 of 9 | |
| Raduga-2St. Petersburg | 3 of 8 | |
| Tsvetochnaya Data CenterSt. Petersburg | 3 of 8 | |
| Miran-1Санкт-Петербург | 1 of 5 | |
| RETNNet OV DCSt. Petersburg | 1 of 2 | |
| XelentSt. Petersburg | 0 of 2 | |
| Linxdatacenter (Saint-Petersburg)St. Petersburg | 1 of 1 | |
| Miran-2St. Petersburg | 0 of 1 | |
| Prometey Ltd SPB MM11St. Petersburg | 1 of 1 | |
| COD BM-18St.Petersburg | No exchange | |
| Prometey Ltd SPB A6St.Petersburg | No exchange |