ixreport

baragoon networks: PeeringDB fix list

AS215887 · peeringdb.com/net/34817

PeeringDB

7 things to fix in baragoon networks's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on baragoon networks's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

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

  1. Netherlands 3AM Network IX Amsterdam, Netherlands · PeeringDB 5023From its IX-F export and website members list
    IPv491.213.211.73
    IPv62001:7f8:17d::73
    Speed1000 Mbps (1G)
    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 (5)

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. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDBnone185.1.125.185
    • In the entry with IPv6 2001:7f8:d0::3:4b4f:1: set IPv4 to 185.1.125.185 (now empty).
  2. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDB2001:7f8:ca:1:0:21:5887:12001:7f8:ca:1:0:21:5887:1 2001:7f8:ca:1:0:21:5887:2
    Port speed differs1G1G + 100M
    • Add an entry: IPv4 –, IPv6 2001:7f8:ca:1:0:21:5887:2, speed 100 (100M), 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. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512
    ProblemPeeringDB hasThe export has
    Port speed differs1G10G
    • In the entry with IPv4 185.1.160.189: set Speed to 10000 (10G) (now 1000).

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

  4. United Kingdom LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    Port speed differs250M1G
    • In the entry with IPv4 5.57.82.124: set Speed to 1000 (1G) (now 250).

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

  5. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.119.100193.239.119.55 193.239.119.100
    IPv6 address missing from PeeringDB2001:7f8:13::a521:5887:22001:7f8:13::a521:5887:1 2001:7f8:13::a521:5887:2
    • Add an entry: IPv4 193.239.119.55, IPv6 2001:7f8:13::a521:5887:1, 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 baragoon networks has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Ukraine BEE-IX Lviv, Ukraine · PeeringDB 4105Not on its website members list
    IPv4–
    IPv62001:7f8:11f:be00:215:887:0:1
    Speed1000 Mbps (1G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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