ixreport

JSC SEVEREN-TELECOM: PeeringDB fix list

AS35000 · peeringdb.com/net/1610

PeeringDB

4 things to fix in JSC SEVEREN-TELECOM's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on JSC SEVEREN-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 (4)

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 AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs10G3G
    • In the entry with IPv4 80.249.209.5: set Speed to 3000 (3G) (now 10000).

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

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.224.36 178.18.224.37178.18.224.36 178.18.224.37 178.18.225.37
    IPv6 address missing from PeeringDB2a03:5f80:4::224:36 2a03:5f80:4::224:372a03:5f80:4::224:36 2a03:5f80:4::224:37 2a03:5f80:4::225:37
    Port speed differs2 × 20G3 × 10G
    • In the entry with IPv4 178.18.224.36: set Speed to 10000 (10G) (now 20000).
    • In the entry with IPv4 178.18.224.37: set Speed to 10000 (10G) (now 20000).
    • Add an entry: IPv4 178.18.225.37, IPv6 2a03:5f80:4::225:37, speed 10000 (10G), 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 Moscow Moscow, Russia · PeeringDB 100
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB195.208.208.119195.208.208.119 195.208.208.165
    IPv6 address missing from PeeringDB2001:7f8:20:101::208:1192001:7f8:20:101::208:119 2001:7f8:20:101::208:165
    • Add an entry: IPv4 195.208.208.165, IPv6 2001:7f8:20:101::208:165, 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.

  4. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.226.102.78194.226.100.78 194.226.102.78
    IPv6 address missing from PeeringDB2001:7f8:20:202::102:782001:7f8:20:201::100:78 2001:7f8:20:202::102:78
    • Add an entry: IPv4 194.226.100.78, IPv6 2001:7f8:20:201::100:78, 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/35000/: 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.