PHILUNET GmbH: PeeringDB fix list
AS205112 · peeringdb.com/net/15111
3 things to fix in PHILUNET GmbH's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on PHILUNET 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 PHILUNET 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 IPv6 address differs 2001:7f8:3d:0:3:2138:0:1 2001:7f8:3d:0:3:c22:0:1 - In the entry with IPv4 185.1.210.57: set IPv6 to 2001:7f8:3d:0:3:c22:0:1 (now 2001:7f8:3d:0:3:2138:0:1).
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 193.189.83.102: set Speed to 1000 (1G) (now 10000).
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/205112/: 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.