net services: PeeringDB fix list
AS42965 · peeringdb.com/net/10724
8 things to fix in net services's PeeringDB record, from what its exchanges publish: 7 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on net services'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 (7)
On the exchange's own member list, but not in net services's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.0.4.7 IPv6 2001:7f8:139::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.170.165 IPv6 2001:7f8:9e::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.0.17.3 IPv6 2001:7f8:143::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.0.5.9 IPv6 2001:7f8:13a::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
DE-CIX Kristiansand Kristiansand, Norway · PeeringDB 4042From its IX-F export and website members list
IPv4 185.0.6.4 IPv6 2001:7f8:13b::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.1.208.164 IPv6 2001:7f8:44::a7d5:0:1 Speed 100000 Mbps (100G) RS peer Yes -
IPv4 185.0.7.7 IPv6 2001:7f8:13c::a7d5:0:1 Speed 100000 Mbps (100G) 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 IPv4 address missing from PeeringDB 185.1.210.58 185.1.210.17 185.1.210.58 IPv6 address missing from PeeringDB 2001:7f8:3d::a7d5:0:2 2001:7f8:3d::a7d5:0:1 2001:7f8:3d::a7d5:0:2 Port speed differs 40G 2 × 100G - In the entry with IPv4 185.1.210.58: set Speed to 100000 (100G) (now 40000).
- Add an entry: IPv4 185.1.210.17, IPv6 2001:7f8:3d::a7d5:0:1, speed 100000 (100G), RS peer yes.
From ixreport.com/net/42965/: 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.