ixreport

Okko: PeeringDB fix list

AS211609 · peeringdb.com/net/26560

PeeringDB

5 things to fix in Okko's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Okko'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 (2)

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

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export
    IPv4194.85.107.51
    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.

  2. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380From its IX-F export
    IPv4193.232.140.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.

Correct these entries (3)

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
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:149
    Port speed differs100G200G
    • In the entry with IPv4 178.18.224.149: set IPv6 to 2a03:5f80:4::224:149 (now empty); set Speed to 200000 (200G) (now 100000).

    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 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.208.185 195.208.209.245195.208.208.35 195.208.208.185 195.208.209.243 195.208.209.245 195.208.210.173
    • Add an entry: IPv4 195.208.209.243, IPv6 –, RS peer yes.
    • Add an entry: IPv4 195.208.210.173, IPv6 –, RS peer yes.
    • Add an entry: IPv4 195.208.208.35, IPv6 –, 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.

  3. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.232.87.65193.232.87.65 193.232.87.121
    • Add an entry: IPv4 193.232.87.121, IPv6 –, 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.

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