ixreport

Nizhnetagilskie Kompyuternye Seti

AS49218

Nizhnetagilskie Kompyuternye Seti LLC

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

Tools: Where can I peer with Nizhnetagilskie Kompyuternye Seti? · Where should Nizhnetagilskie Kompyuternye Seti peer next? · Compare Nizhnetagilskie Kompyuternye Seti with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Nizhnetagilskie Kompyuternye Seti's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Nizhnetagilskie Kompyuternye Seti'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 (1)

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 GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.233.8178.18.225.221 178.18.233.8
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:221 2a03:5f80:4:1::233:8
    Port speed differs20G20G + 10G
    • In the entry with IPv4 178.18.233.8: set IPv6 to 2a03:5f80:4:1::233:8 (now empty); set Speed to 10000 (10G) (now 20000).
    • Add an entry: IPv4 178.18.225.221, IPv6 2a03:5f80:4::225:221, speed 20000 (20G), 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

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

Map

Where Nizhnetagilskie Kompyuternye Seti'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 60G across 4 exchanges.

Russia CLOUD-IX EKT Ekaterinburg, Russia 31.28.29.31 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.233.8 20G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.44 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.210.44 20G Yes PeeringDB only

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

These exchanges have a switch in a facility where Nizhnetagilskie Kompyuternye Seti lists itself in PeeringDB, but don't have Nizhnetagilskie Kompyuternye Seti 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 CLOUD-IX MSKMoscow, Russia 52 EKB, Uralcod
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 EKB, Uralcod
Facilities (1)

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

Russia EKB, UralcodEkaterinburg 3 of 5