Priobskie seti: PeeringDB fix list

AS43330

One thing to fix in Priobskie seti's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

AS43330 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 Priobskie seti's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223From its IX-F export
    IPv4193.232.87.104
    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.

From ixreport.com/net/43330/: 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.