Adylnet Telecom - AS28283: PeeringDB fix list
AS28283 · peeringdb.com/net/3427
6 things to fix in Adylnet Telecom - AS28283's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Adylnet Telecom - AS28283'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 Adylnet Telecom - AS28283's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::6e7b:1 Speed Not published RS peer Yes
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.
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 149.112.11.103: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 206.53.202.160: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 20G 100G - In the entry with IPv4 80.81.194.199: set Speed to 100000 (100G) (now 20000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 185.1.47.140: set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 100G - In the entry with IPv4 206.82.104.231: set Speed to 100000 (100G) (now 10000).
From ixreport.com/net/28283/: 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.