NeoProtect: PeeringDB fix list

AS199414 · peeringdb.com/net/33066

PeeringDB

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

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

  1. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990From its IX-F export and website members list
    IPv4185.1.184.97
    IPv62001:7f8:134::97
    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.

  2. Netherlands LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308From its IX-F export and website members list
    IPv4185.1.32.113
    IPv62001:7f8:8f::a519:9414:1
    Speed10000 Mbps (10G)
    RS peerYes

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