DIGI RO: PeeringDB fix list
AS8708 · peeringdb.com/net/110
3 things to fix in DIGI RO's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on DIGI RO'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 DIGI RO's PeeringDB record. Add one entry per connection with these values.
-
IPv4 194.53.172.114 194.53.172.119 IPv6 2001:7f8:26::a500:8708:1 2001:7f8:26::a500:8708:2 Speed Not published RS peer Not published The exchange lists several addresses but not which go together: add one entry for each IPv4 and IPv6 pair.
-
2 connections, so 2 entries:
IPv4 80.81.192.87 IPv6 2001:7f8::2204:0:1 Speed 200000 Mbps (200G) RS peer Yes IPv4 80.81.197.4 IPv6 2001:7f8::2204:0:2 Speed 200000 Mbps (200G) RS peer Yes
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 Address belongs to another network in PeeringDB 80.81.192.87 is AS6910 DIGI BORDER 80.81.192.87 Address belongs to another network in PeeringDB 80.81.197.4 is AS6910 DIGI BORDER 80.81.197.4 Address belongs to another network in PeeringDB 2001:7f8::2204:0:1 is AS6910 DIGI BORDER 2001:7f8::2204:0:1 Address belongs to another network in PeeringDB 2001:7f8::2204:0:2 is AS6910 DIGI BORDER 2001:7f8::2204:0:2 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/8708/: 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.