SECUREPEAK: PeeringDB fix list
AS216096 · peeringdb.com/net/40174
5 things to fix in SECUREPEAK's PeeringDB record, from what its exchanges publish: 2 to add, 3 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on SECUREPEAK'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 SECUREPEAK's PeeringDB record. Add one entry per connection with these values.
-
4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members listIPv4 – IPv6 2001:7f8:d0::3:4c20:1 Speed Not published RS peer Yes -
IPv4 206.80.238.199 IPv6 2001:504:91::199 Speed Not published RS peer Not published
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 30M - In the entry with IPv4 218.100.76.30: set Speed to 30 (30M) (now 10000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 20M - In the entry with IPv4 218.100.78.21: set Speed to 20 (20M) (now 10000).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
-
Problem PeeringDB has The export has Address belongs to another network in PeeringDB 195.66.237.22 is AS25061 Associated Networks (UK) Ltd 195.66.237.22 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/216096/: 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.