LLC G&G-Telecom: PeeringDB fix list

AS207239 · peeringdb.com/net/34436

PeeringDB

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

Make the changes on LLC G&G-Telecom's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (1)

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. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:20:201::100:37 2001:7f8:20:202::102:37
    • In the entry with IPv4 194.226.100.37: set IPv6 to 2001:7f8:20:201::100:37 (now empty).
    • In the entry with IPv4 194.226.102.37: set IPv6 to 2001:7f8:20:202::102:37 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If LLC G&G-Telecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100Not on its IX-F export
    IPv4195.208.210.137
    IPv6–
    Speed10000 Mbps (10G)

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