ixreport

BeGet

AS198610

BeGet LLC

6Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
EnterpriseType
OpenPeering policy
6Using the route servers
2To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with BeGet? · Where should BeGet peer next? · Compare BeGet with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

2 things to fix in BeGet's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-11-19 12:40 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 × 10G4 × 100G
    • In the entry with IPv4 178.18.224.125: set IPv6 to 2a03:5f80:4::224:125 (now empty); set Speed to 100000 (100G) (now 10000).
    • 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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where BeGet's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 140G across 6 exchanges.

Russia CLOUD-IX SPB St. Petersburg, Russia 31.28.18.208 10G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.224.125
178.18.224.130
2 × 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Russia MSK-IX Moscow Moscow, Russia 195.208.210.141 10G Yes PeeringDB only
Russia MSK-IX Saint-Petersburg St.Petersburg, Russia 194.226.100.141
194.226.102.141
2 × 10G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB
Russia PITER-IX Moscow Moscow, Russia 185.0.13.125 40G Yes PeeringDB
Russia PITER-IX Saint-Petersburg Saint-Petersburg, Russia 185.1.153.89 40G Yes PeeringDB

BeGet lists no facilities in PeeringDB.