buerodata: PeeringDB fix list

AS203924 · peeringdb.com/net/26102

PeeringDB

One thing to fix in buerodata's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

Make the changes on buerodata'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 buerodata's PeeringDB record. Add one entry per connection with these values.

  1. Germany MegaIX Dusseldorf Dusseldorf, Germany · PeeringDB 91From its IX-F export

    2 connections, so 2 entries:

    IPv4194.146.118.19
    IPv62001:7f8:8:0:3:1c94:0:3
    SpeedNot published
    RS peerYes
    IPv4194.146.118.35
    IPv62001:7f8:8:0:3:1c94:0:4
    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.

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