NUXOA GmbH: PeeringDB fix list
AS51202 · peeringdb.com/net/38026
4 things to fix in NUXOA GmbH's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on NUXOA GmbH'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 NUXOA GmbH's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (2)
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 100G 10G - In the entry with IPv4 185.0.27.15: set Speed to 10000 (10G) (now 100000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 20G 10G - In the entry with IPv4 185.0.30.58: 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.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If NUXOA GmbH has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.81.104.176 IPv6 2602:fed2:fff:ffff::176 Speed 10000 Mbps (10G)
From ixreport.com/net/51202/: 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.