4830.org e. V.: PeeringDB fix list
AS206813 · peeringdb.com/net/14026
5 things to fix in 4830.org e. V.'s PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on 4830.org e. V.'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 4830.org e. V.'s PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.208.104 IPv6 2001:7f8:44:0:3:27dd:0:1 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 193.189.82.142 IPv6 2001:7f8:33::a120:6813:1 Speed 100 Mbps (100M) 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.
Correct these entries (3)
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 1G 10G - In the entry with IPv4 185.1.170.97: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 3G + 500M 2 × 10G - In the entry with IPv4 80.81.196.10: set Speed to 10000 (10G) (now 500).
- In the entry with IPv4 80.81.196.86: set Speed to 10000 (10G) (now 3000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 185.1.210.108: set Speed to 10000 (10G) (now 1000).
From ixreport.com/net/206813/: 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.