ixreport

link up isp_mow

AS213499

2Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
2Using the route servers
2To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

Tools: Where can I peer with link up isp_mow? · Where should link up isp_mow peer next? · Compare link up isp_mow with another network

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

PeeringDB fix list Printable page · CSV

2 things to fix in link up isp_mow's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-11-19 12:40 UTC.

AS213499 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (2)

On the exchange's own member list, but not in link up isp_mow's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.226.171
    IPv62a03:5f80:4::226:171
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.226.176
    IPv62a03:5f80:4::226:176
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4195.208.210.221
    IPv62001:7f8:20:101::210:221
    SpeedNot published
    RS peerYes
    IPv4195.208.209.21
    IPv62001:7f8:20:101::209:21
    SpeedNot published
    RS peerYes

    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

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

Map

Where link up isp_mow'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 10G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.226.171
178.18.226.176
2a03:5f80:4::226:171
2a03:5f80:4::226:176
10G Yes Not in PeeringDB
Russia MSK-IX Moscow Moscow, Russia 195.208.209.21
195.208.210.221
2001:7f8:20:101::209:21
2001:7f8:20:101::210:221
Yes Not in PeeringDB