ixreport

BeGet: PeeringDB fix list

AS198610 · peeringdb.com/net/9646

PeeringDB

3 things to fix in BeGet's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on BeGet'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 (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
    IPv4 address missing from PeeringDB178.18.224.125 178.18.224.130178.18.224.125 178.18.224.130 178.18.226.229 178.18.226.234
    IPv6 address missing from PeeringDBnone2a03:5f80:4::224:125 2a03:5f80:4::224:130 2a03:5f80:4::226:229 2a03:5f80:4::226:234
    Port speed differs2 × 10G3 × 100G + 10G
    • In the entry with IPv4 178.18.224.125: set IPv6 to 2a03:5f80:4::224:125 (now empty).
    • In the entry with IPv4 178.18.224.130: set IPv6 to 2a03:5f80:4::224:130 (now empty); set Speed to 100000 (100G) (now 10000).
    • Add an entry: IPv4 178.18.226.229, IPv6 2a03:5f80:4::226:229, speed 100000 (100G), RS peer yes.
    • Add an entry: IPv4 178.18.226.234, IPv6 2a03:5f80:4::226:234, speed 100000 (100G), 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.

  2. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB194.226.100.141 194.226.102.141194.226.100.141 194.226.100.144 194.226.102.141 194.226.102.144
    IPv6 address missing from PeeringDBnone2001:7f8:20:201::100:141 2001:7f8:20:201::100:144 2001:7f8:20:202::102:141 2001:7f8:20:202::102:144
    • In the entry with IPv4 194.226.100.141: set IPv6 to 2001:7f8:20:201::100:141 (now empty).
    • In the entry with IPv4 194.226.102.141: set IPv6 to 2001:7f8:20:202::102:141 (now empty).
    • Add an entry: IPv4 194.226.100.144, IPv6 2001:7f8:20:201::100:144, RS peer yes.
    • Add an entry: IPv4 194.226.102.144, IPv6 2001:7f8:20:202::102:144, 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.

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If BeGet 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.141
    IPv6–
    Speed10000 Mbps (10G)

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