ixreport

DACS NX: PeeringDB fix list

AS6515 · peeringdb.com/net/22730

PeeringDB

4 things to fix in DACS NX's PeeringDB record, from what its exchanges publish: 2 to check, 2 at exchanges that look shut down. As of 2026-10-08 21:56 UTC.

Make the changes on DACS NX'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 (2)

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

  1. United States FCIX Fremont, United States · PeeringDB 2163Not on its website members list
    IPv4206.80.238.171
    IPv62001:504:91::171
    Speed10000 Mbps (10G)

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

  2. United States SFMIX San Francisco, United States · PeeringDB 155Not on its IX-F export or website members list
    IPv4206.197.187.105
    IPv62001:504:30::ba00:6515:1
    Speed10000 Mbps (10G)

Exchanges that look shut down (2)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. United States DACS-IX Northghost New York, United States · PeeringDB 4609

    Only the operator's own networks

    IPv4149.112.49.10
    IPv62001:505:148:e514::10
    Speed40000 Mbps (40G)
  2. United States DACS-IX Southghost Orlando, United States · PeeringDB 4610

    Only the operator's own networks

    IPv4149.112.83.10
    IPv62001:505:148:e513::10
    Speed40000 Mbps (40G)

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