BeGet
AS198610
BeGet LLC
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 178.18.224.125 178.18.224.130 178.18.224.125 178.18.224.130 178.18.226.229 178.18.226.234 IPv6 address missing from PeeringDB none 2a03:5f80:4::224:125 2a03:5f80:4::224:130 2a03:5f80:4::226:229 2a03:5f80:4::226:234 Port speed differs 2 × 10G 4 × 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 194.226.100.141 194.226.102.141 194.226.100.141 194.226.100.144 194.226.102.141 194.226.102.144 IPv6 address missing from PeeringDB none 2001: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
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 6 |
| Nov 18, 2026 | 6 |
| Nov 17, 2026 | 6 |
| Nov 16, 2026 | 6 |
| Nov 15, 2026 | 6 |
| Nov 14, 2026 | 6 |
| Nov 13, 2026 | 6 |
| Nov 12, 2026 | 6 |
| Nov 11, 2026 | 6 |
| Nov 10, 2026 | 6 |
| Nov 9, 2026 | 6 |
| Nov 8, 2026 | 6 |
| Nov 7, 2026 | 6 |
| Nov 6, 2026 | 6 |
| Nov 5, 2026 | 6 |
| Nov 4, 2026 | 6 |
| Nov 3, 2026 | 6 |
| Nov 2, 2026 | 6 |
| Nov 1, 2026 | 6 |
| Oct 31, 2026 | 6 |
| Oct 30, 2026 | 6 |
| Oct 29, 2026 | 6 |
| Oct 28, 2026 | 6 |
| Oct 27, 2026 | 6 |
| Oct 26, 2026 | 6 |
| Oct 25, 2026 | 6 |
| Oct 24, 2026 | 6 |
| Oct 23, 2026 | 6 |
| Oct 22, 2026 | 6 |
| Oct 21, 2026 | 6 |
| Oct 20, 2026 | 6 |
| Oct 19, 2026 | 6 |
| Oct 18, 2026 | 6 |
| Oct 17, 2026 | 6 |
| Oct 16, 2026 | 6 |
| Oct 15, 2026 | 6 |
| Oct 14, 2026 | 6 |
| Oct 13, 2026 | 6 |
| Oct 12, 2026 | 6 |
| Oct 11, 2026 | 6 |
| Oct 10, 2026 | 6 |
| Oct 9, 2026 | 6 |
| Oct 8, 2026 | 6 |
| Oct 7, 2026 | 6 |
| Oct 6, 2026 | 6 |
| Oct 5, 2026 | 6 |
| Oct 4, 2026 | 6 |
| Oct 3, 2026 | 6 |
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.
| CLOUD-IX SPB St. Petersburg, Russia | 10G | PeeringDB | |
| GNM-IX Amsterdam, Netherlands | 2 × 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs | |
| MSK-IX Moscow Moscow, Russia | 10G | PeeringDB only | |
| MSK-IX Saint-Petersburg St.Petersburg, Russia | 2 × 10G | Both IPv4 not in PeeringDBIPv6 not in PeeringDB | |
| PITER-IX Moscow Moscow, Russia | 40G | PeeringDB | |
| PITER-IX Saint-Petersburg Saint-Petersburg, Russia | 40G | PeeringDB |
BeGet lists no facilities in PeeringDB.