Digital Systems: PeeringDB fix list
AS3245 · peeringdb.com/net/25350
3 things to fix in Digital Systems's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Digital Systems's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
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 10G 1G - In the entry with IPv4 185.1.30.34: set Speed to 1000 (1G) (now 10000).
- Add an entry: IPv4 –, IPv6 2001:7f8:8e:4::34, speed 1000 (1G), RS peer yes.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 193.169.198.104 193.169.198.104 193.169.198.110 IPv6 address missing from PeeringDB 2001:7f8:58::cad:0:1 2001:7f8:58::cad:0:1 2001:7f8:58::cad:0:2 - Add an entry: IPv4 193.169.198.110, IPv6 2001:7f8:58::cad:0:2.
-
Problem PeeringDB has The export has IPv6 address differs 2001:67c:29f0::3245:1 2001:67c:29f0::3:245:1 - In the entry with IPv4 185.1.226.38: set IPv6 to 2001:67c:29f0::3:245:1 (now 2001:67c:29f0::3245:1).
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/3245/: 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.