ixreport

NODEX

AS29329

NODEX Limited

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

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

Make the changes on NODEX'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 Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.226.100.60194.226.100.60 194.226.102.60
    IPv6 address missing from PeeringDB2001:7f8:20:201::100:602001:7f8:20:201::100:60 2001:7f8:20:202::102:60
    • Add an entry: IPv4 194.226.102.60, IPv6 2001:7f8:20:202::102:60, 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

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

Map

Where NODEX'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 70G across 7 exchanges.

Russia MSK-IX Moscow Moscow, Russia 195.208.208.252 2001:7f8:20:101::208:252 10G Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.60 2001:7f8:20:201::100:60 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Finland PITER-IX Helsinki Helsinki, Finland 193.27.37.30 10G Yes PeeringDB
Ukraine PITER-IX Kiev Киев, Ukraine 146.185.252.66 10G Yes PeeringDB
Latvia PITER-IX Riga Riga, Latvia 193.27.39.120 10G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.152.38 10G Yes PeeringDB
Estonia PITER-IX Tallinn Tallinn, Estonia 37.9.49.82 10G Yes PeeringDB

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

These exchanges have a switch in a facility where NODEX lists itself in PeeringDB, but don't have NODEX 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.

Facilities (3)

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

Russia IVC ORW Saint-PetersburgSt. Petersburg 2 of 10
Russia Bolshaya Morskaya 18St. Petersburg 2 of 9
Russia Moscow M9Moscow 2 of 9