MyRootPW.com: PeeringDB fix list

AS39409 · peeringdb.com/net/31933

PeeringDB

4 things to fix in MyRootPW.com's PeeringDB record, from what its exchanges publish: 2 to add, 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on MyRootPW.com'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 MyRootPW.com's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756From its IX-F export and website members list
    IPv4185.1.147.199
    IPv62001:7f8:ca:1::199
    Speed1000 Mbps (1G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Germany FogIXP Frankfurt Frankfurt, Germany · PeeringDB 4200From its IX-F export and website members list
    IPv4185.0.30.46
    IPv62001:7f8:11c:1:0:3:9409:1
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Check these entries (2)

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

  1. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512Not on its IX-F export
    IPv4185.1.160.167
    IPv62001:7f8:10f::99f1:167
    Speed10000 Mbps (10G)
  2. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990Not on its IX-F export or website members list
    IPv4185.1.184.31
    IPv62001:7f8:134::31
    Speed10000 Mbps (10G)

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