DIGI BORDER: PeeringDB fix list
AS6910 · peeringdb.com/net/2521
5 things to fix in DIGI BORDER's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct, 3 to check. As of 2026-10-08 21:56 UTC.
Make the changes on DIGI BORDER'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 DIGI BORDER's PeeringDB record. Add one entry per connection with these values.
-
IPv4 86.104.125.100 IPv6 2001:7f8:64:225::8708:1 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.
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 Port speed differs 10G 20G - In the entry with IPv4 217.29.67.220: set Speed to 20000 (20G) (now 10000).
Check these entries (3)
In PeeringDB, but on none of the exchange's own lists. If DIGI BORDER has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 185.1.119.27 IPv6 2001:7f8:10a::dfb5:0:2 Speed 10000 Mbps (10G) IPv4 185.1.119.6 IPv6 2001:7f8:10a::dfb5:0:1 Speed 10000 Mbps (10G) -
IPv4 80.81.192.87 IPv6 2001:7f8::2204:0:1 Speed 200000 Mbps (200G) IPv4 80.81.197.4 IPv6 2001:7f8::2204:0:2 Speed 200000 Mbps (200G) -
IPv4 185.1.192.122 IPv6 2001:7f8:a0::dfb5:0:1 Speed 200000 Mbps (200G) IPv4 185.1.192.243 IPv6 2001:7f8:a0::dfb5:0:2 Speed 100000 Mbps (100G)
From ixreport.com/net/6910/: 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.