ixreport

my.games_beg

AS200784

2Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
2Using the route servers
3To fix in PeeringDB

This network has no PeeringDB record; it was found on exchanges' own member lists.

Tools: Where can I peer with my.games_beg? · Where should my.games_beg peer next? · Compare my.games_beg with another network

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

PeeringDB fix list Printable page · CSV

3 things to fix in my.games_beg's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

AS200784 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (2)

On the exchange's own member list, but not in my.games_beg's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.237.61
    IPv62a03:5f80:4:2::237:61
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.237.62
    IPv62a03:5f80:4:2::237:62
    Speed10000 Mbps (10G)
    RS peerYes

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

  2. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4185.1.226.85
    IPv62001:67c:29f0::20:784:1
    SpeedNot published
    RS peerYes
    IPv4185.1.226.87
    IPv62001:67c:29f0::20:784:2
    SpeedNot published
    RS peerYes

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

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. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB185.1.226.85 is AS1820 Wnet Telecom USA185.1.226.85

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    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

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

In the last 30 days my.games_beg joined 1 exchange and left 0. Growing networks

Joined

Map

Where my.games_beg'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 10G, at the 1 of 2 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Netherlands GNM-IX Amsterdam, Netherlands 178.18.237.61
178.18.237.62
2a03:5f80:4:2::237:61
2a03:5f80:4:2::237:62
10G Yes Not in PeeringDB
Bulgaria NetIX Sofia, Bulgaria 185.1.226.85
185.1.226.87
2001:67c:29f0::20:784:1
2001:67c:29f0::20:784:2
Yes Not in PeeringDB Address taken

Recent changes Search them

  • Nov 4, 2026 [IXF] AS200784 my.games_beg now on NetIX's IX-F list
  • Nov 3, 2026 [WEB] AS200784 my.games_beg added to NetIX