ixreport

N-REGION: PeeringDB fix list

AS34223 · peeringdb.com/net/39432

PeeringDB

2 things to fix in N-REGION's PeeringDB record, from what its exchanges publish: 1 to add, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on N-REGION's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

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

  1. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107From its IX-F export

    2 connections, so 2 entries:

    IPv4194.226.102.61
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4194.226.100.61
    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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If N-REGION has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100Not on its IX-F export
    IPv4195.208.209.173
    IPv6–
    Speed10000 Mbps (10G)

From ixreport.com/net/34223/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.