ixreport

NSIX Route Servers: PeeringDB fix list

AS213874 · peeringdb.com/net/37812

PeeringDB

One thing to fix in NSIX Route Servers's PeeringDB record, from what its exchanges publish: 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on NSIX Route Servers's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Check these entries (1)

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

  1. Netherlands NSIX Amsterdam Amsterdam, Netherlands · PeeringDB 4589Not on its website members list
    IPv4193.192.12.1
    IPv62001:7f8:130::1
    Speed10000 Mbps (10G)
    IPv4193.192.12.2
    IPv62001:7f8:130::2
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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