OJSC Telecom-Service: PeeringDB fix list

AS60840

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

AS60840 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 OJSC Telecom-Service's PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    2 connections, so 2 entries:

    IPv4195.208.208.72
    IPv62001:7f8:20:101::208:72
    SpeedNot published
    RS peerYes
    IPv4195.208.210.202
    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/60840/: 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.