ixreport

Cifrovie Seti Urala

AS209307

LLC Cifrovie Seti Urala

12Exchanges
0On an exchange's list, not in PeeringDB
2In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
SelectivePeering policy
12Using the route servers
3To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with Cifrovie Seti Urala? · Where should Cifrovie Seti Urala peer next? · Compare Cifrovie Seti Urala with another network

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

PeeringDB fix list Printable page · CSV

3 things to fix in Cifrovie Seti Urala's PeeringDB record, from what its exchanges publish: 1 to correct, 2 to check. As of 2026-11-19 12:40 UTC.

Make the changes on Cifrovie Seti Urala'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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::227:25
    • In the entry with IPv4 178.18.227.25: set IPv6 to 2a03:5f80:4::227:25 (now empty).

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

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If Cifrovie Seti Urala has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223Not on its IX-F export
    IPv4193.232.87.133
    IPv6–
    Speed20000 Mbps (20G)
  2. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.100.133
    IPv6–
    Speed20000 Mbps (20G)
    IPv4194.226.102.133
    IPv6–
    Speed20000 Mbps (20G)

Exchanges over time

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

Map

Where Cifrovie Seti Urala'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 220G across 12 exchanges.

Russia CLOUD-IX EKT Ekaterinburg, Russia 31.28.29.28 10G Yes PeeringDB
Netherlands Global-IX Amsterdam, Netherlands 109.239.137.204 30G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.227.25 30G Yes Both IPv6 not in PeeringDB
Russia MSK-IX Ekaterinburg Ekaterinburg, Russia 194.85.107.43 10G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.210.133 20G Yes PeeringDB only
Russia MSK-IX Novosibirsk Novosibirsk, Russia 193.232.87.133 20G Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.133
194.226.102.133
2 × 20G Yes PeeringDB only
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.12 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.94 10G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.15.5 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.0.44.151 10G Yes PeeringDB
Russia W-IX Moscow, Russia 193.106.112.226 20G Yes PeeringDB

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

These exchanges have a switch in a facility where Cifrovie Seti Urala lists itself in PeeringDB, but don't have Cifrovie Seti Urala 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; Erlang.Ekb.MS145; DataHouse Ekaterinburg
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 EKB, Uralcod; Erlang.Ekb.MS145
Facilities (3)

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

Russia EKB, UralcodEkaterinburg 3 of 5
Russia Erlang.Ekb.MS145Ekaterinburg 3 of 5
Russia DataHouse EkaterinburgEkaterinburg 1 of 2

Recent changes Search them

  • Oct 13, 2026 [PDB] AS209307 Cifrovie Seti Urala added to PITER-IX Helsinki
  • Oct 13, 2026 [PDB] AS209307 Cifrovie Seti Urala added to PITER-IX Frankfurt
  • Oct 13, 2026 [PDB] AS209307 Cifrovie Seti Urala added to PITER-IX Saint-Petersburg
  • Oct 13, 2026 [PDB] AS209307 Cifrovie Seti Urala added to PITER-IX Moscow