ixreport

M9 COM

AS38984 · M9COM

M9 COM LTD

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

Tools: Where can I peer with M9 COM? · Where should M9 COM peer next? · Compare M9 COM with another network

This network elsewhere: its routes on BGP Report

PeeringDB fix list Printable page · CSV

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

Make the changes on M9 COM'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.225.51178.18.225.50 178.18.225.51
    IPv6 address missing from PeeringDBnone2a03:5f80:4::225:50 2a03:5f80:4::225:51
    • In the entry with IPv4 178.18.225.51: set IPv6 to 2a03:5f80:4::225:51 (now empty).
    • Add an entry: IPv4 178.18.225.50, IPv6 2a03:5f80:4::225:50, speed 10000 (10G), 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 M9 COM'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 30G across 3 exchanges.

Russia Eurasia Peering IX Moscow, Russia 185.232.60.52 10G PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.51 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.45 10G PeeringDB

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

These exchanges have a switch in a facility where M9 COM lists itself in PeeringDB, but don't have M9 COM 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 PITER-IX Saint-PetersburgSaint-Petersburg, Russia 246 Moscow M9
Netherlands Global-IXAmsterdam, Netherlands 138 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 M9 COM lists in PeeringDB, and how many of the exchanges in each it's on.

Russia Moscow M9Moscow 3 of 9