ixreport

Gorodskie seti

AS212487 · Омега Коннект

Gorodskie seti OOO

9Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
9Using the route servers
1To fix in PeeringDB
1Facility in PeeringDB

Tools: Where can I peer with Gorodskie seti? · Where should Gorodskie seti peer next? · Compare Gorodskie seti with another network

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

PeeringDB fix list Printable page · CSV

One thing to fix in Gorodskie seti's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Gorodskie 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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:85
    • In the entry with IPv4 178.18.225.85: set IPv6 to 2a03:5f80:4::225:85 (now empty).

    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

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

Map

Where Gorodskie 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 90G across 9 exchanges.

Netherlands Global-IX Amsterdam, Netherlands 109.239.136.247 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.85 10G Yes Both IPv6 not in PeeringDB
Germany PITER-IX Frankfurt Frankfurt, Germany 31.44.186.175 10G Yes PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.241 10G Yes PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.54 10G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.128 10G Yes PeeringDB
Russia PITER-IX Rostov Rostov, Russia 193.27.38.54 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.61 10G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.194 10G Yes PeeringDB

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

These exchanges have a switch in a facility where Gorodskie seti lists itself in PeeringDB, but don't have Gorodskie 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 MSK-IX MoscowMoscow, Russia 638 Moscow M9
Russia Eurasia Peering IXMoscow, Russia 136 Moscow M9
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (1)

The buildings Gorodskie seti lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 4 of 9