ixreport

UNDEFINED

AS201282

Follow changes
1Exchange
1On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
1Using the route servers
1To fix in PeeringDB

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

Tools: Where can I peer with UNDEFINED? · Where should UNDEFINED peer next?

PeeringDB fix list Printable page

One thing to fix in UNDEFINED's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-09 12:26 UTC.

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

Add these exchanges (1)

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

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.211.38
    IPv6–
    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

This chart fills in as daily counts build up; the first was Oct 9, 2026.

Exchanges
Russia MSK-IX Moscow Moscow, Russia 195.208.211.38 Yes Not in PeeringDB

Recent changes Search them

  • Oct 9, 2026 [IXF] AS201282 UNDEFINED added to MSK-IX Moscow