ixreport

NETRACK

AS61400 · NETRACK

"Start" LLC

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
–Type
OpenPeering policy
2Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with NETRACK? · Where should NETRACK peer next? · Compare NETRACK 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 NETRACK's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on NETRACK'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. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.209.195195.208.209.195 195.208.210.148
    IPv6 address missing from PeeringDB2001:7f8:20:101::209:1952001:7f8:20:101::209:195 2001:7f8:20:101::210:148
    • Add an entry: IPv4 195.208.210.148, IPv6 2001:7f8:20:101::210:148, 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

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

Map

Where NETRACK'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 200G across 3 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.14 80G PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.243 2a03:5f80:4::226:243 60G Yes Both
Russia MSK-IX Moscow Moscow, Russia 195.208.209.195 2001:7f8:20:101::209:195 60G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

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

These exchanges have a switch in a facility where NETRACK lists itself in PeeringDB, but don't have NETRACK 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 Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Russia PITER-IX MoscowMoscow, Russia 243 Moscow M9; IXcellerate MOS1
Netherlands Global-IXAmsterdam, Netherlands 138 Moscow M9; StoreData; IXcellerate MOS1
Russia W-IXMoscow, Russia 66 Moscow M9
Russia CLOUD-IX MSKMoscow, Russia 52 Moscow M9; StoreData; IXcellerate MOS1
Russia SFO-IXBarnaul, Novosibirsk, Russia 30 Moscow M9
Facilities (3)

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

Russia Moscow M9Moscow 3 of 9
Russia IXcellerate MOS1Moscow 3 of 6
Russia StoreDataMoscow 2 of 4