DGNET: PeeringDB fix list
AS57608 · peeringdb.com/net/11317
3 things to fix in DGNET's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on DGNET'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 DGNET's PeeringDB record. Add one entry per connection with these values.
-
IPv4 89.46.146.39 IPv6 2001:678:3ac::694 Speed 100000 Mbps (100G) 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.
-
IPv4 195.149.233.171 IPv6 2001:7f8:27::5:7608:1 Speed Not published RS peer Not published 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 (1)
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 missing from PeeringDB none 2001:7f8:5b::99 Port speed differs 10G 40G - In the entry with IPv4 178.216.40.99: set IPv6 to 2001:7f8:5b::99 (now empty); set Speed to 40000 (40G) (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/57608/: 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.