ixreport

Cyprea: PeeringDB fix list

AS147039 · peeringdb.com/net/28030

PeeringDB

2 things to fix in Cyprea's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on Cyprea'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 (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.

  1. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.125.214none
    • In the entry with IPv4 185.1.125.214: set IPv4 to (empty) (now 185.1.125.214).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If Cyprea has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214Not on its IX-F export or website members list
    IPv4185.1.171.44
    IPv62001:7f8:9e:0:2:3e5f:0:1
    Speed1000 Mbps (1G)

From ixreport.com/net/147039/: 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.