oja.at: PeeringDB fix list

AS39912 · peeringdb.com/net/1772

5 things to fix in oja.at's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on oja.at'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 (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.

AAIX Klagenfurt, Austria · PeeringDB 377

Problem PeeringDB has The export has

Port speed differs 40G 20G
- In the entry with IPv4 193.37.144.1: set Speed to 20000 (20G) (now 40000).
DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.1.170.20: set Speed to 100000 (100G) (now 1000).
DE-CIX Hamburg Hamburg, Germany · PeeringDB 74

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.1.210.29: set Speed to 100000 (100G) (now 1000).
DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.1.48.24: set Speed to 100000 (100G) (now 1000).
DE-CIX Munich Munich, Germany · PeeringDB 248

Problem PeeringDB has The export has

Port speed differs 1G 100G
- In the entry with IPv4 185.1.208.28: set Speed to 100000 (100G) (now 1000).

Problem	PeeringDB has	The export has
Port speed differs	40G	20G

Problem	PeeringDB has	The export has
Port speed differs	1G	100G

Problem	PeeringDB has	The export has
Port speed differs	1G	100G

Problem	PeeringDB has	The export has
Port speed differs	1G	100G

Problem	PeeringDB has	The export has
Port speed differs	1G	100G

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