LLC "Tvoi Telecom": PeeringDB fix list

AS201211 · peeringdb.com/net/36845

PeeringDB

3 things to fix in LLC "Tvoi Telecom"'s PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on LLC "Tvoi Telecom"'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 LLC "Tvoi Telecom"'s PeeringDB record. Add one entry per connection with these values.

  1. Russia MSK-IX Samara Samara, Russia · PeeringDB 379From its IX-F export
    IPv4193.232.135.49
    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 (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. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs10.24G10G
    • In the entry with IPv4 178.18.225.168: set Speed to 10000 (10G) (now 10240).

    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.109195.208.208.109 195.208.210.197
    • Add an entry: IPv4 195.208.210.197, 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/201211/: 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.