ixreport

Orange Business Services Russia & CIS: PeeringDB fix list

AS2854 · peeringdb.com/net/3142

PeeringDB

3 things to fix in Orange Business Services Russia & CIS's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Orange Business Services Russia & CIS'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 Orange Business Services Russia & CIS's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Kazan Kazan, Russia · PeeringDB 398From its IX-F export
    IPv4194.190.119.11
    IPv62001:7f8:20:801::119:11
    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 (2)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs4G100G
    • In the entry with IPv4 80.81.193.97: set Speed to 100000 (100G) (now 4000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 2G12G + 10G
    • In the entry with IPv4 178.18.224.112: set Speed to 12000 (12G) (now 2000).
    • In the entry with IPv4 178.18.226.247: set Speed to 10000 (10G) (now 2000).

    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/2854/: 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.