DACS-NX Legacy Network: PeeringDB fix list

AS40217 · peeringdb.com/net/15034

PeeringDB

4 things to fix in DACS-NX Legacy Network's PeeringDB record, from what its exchanges publish: 3 to add, 1 to correct. As of 2026-10-08 20:58 UTC.

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

On the exchange's own member list, but not in DACS-NX Legacy Network's PeeringDB record. Add one entry per connection with these values.

  1. United States FCIX Fremont, United States · PeeringDB 2163From its website members list
    IPv4206.80.238.171
    IPv62001:504:91::171
    SpeedNot published
    RS peerNot published
  2. United States FREMIX Fremont, United States · PeeringDB 3685From its website members list
    IPv4149.112.29.105
    IPv62001:504:125:e0::105
    SpeedNot published
    RS peerNot published
  3. United States SFMIX San Francisco, United States · PeeringDB 155From its IX-F export and website members list
    IPv4206.197.187.105
    IPv62001:504:30::ba04:217:1
    Speed10000 Mbps (10G)
    RS peerNot published

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. United States SFMIX San Francisco, United States · PeeringDB 155
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.197.187.105 is AS6515 DACS NX206.197.187.105

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

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