Geckonet: PeeringDB fix list
AS198401 · peeringdb.com/net/11853
3 things to fix in Geckonet's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Geckonet'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 (2)
On the exchange's own member list, but not in Geckonet's PeeringDB record. Add one entry per connection with these values.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members listIPv4 193.239.119.42 IPv6 2001:7f8:13::a519:8401:1 Speed Not published 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.
-
IPv4 195.149.233.209 IPv6 – Speed Not published RS peer Not published 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.
-
Problem PeeringDB has The export has Port speed differs 20G 10G - In the entry with IPv4 89.46.144.195: set Speed to 10000 (10G) (now 20000).
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/198401/: 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.