NVIDIA NGC NSV: PeeringDB fix list

AS398037 · peeringdb.com/net/27987

PeeringDB

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

Make the changes on NVIDIA NGC NSV'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 (4)

On the exchange's own member list, but not in NVIDIA NGC NSV's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26From its IX-F export and website members list
    IPv480.249.214.56
    IPv62001:7f8:1:0:a500:39:8037:1
    Speed100000 Mbps (100G)
    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. United States Any2East Washington DC, Reston, Boston, New York, Atlanta, United States · PeeringDB 204From its website members list
    IPv4206.51.40.67
    IPv62001:504:13:1::67
    SpeedNot published
    RS peerNot published
  3. United States Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142From its website members list
    IPv4206.72.211.126 206.72.211.230
    IPv62001:504:13::211:126 2001:504:13::211:230
    SpeedNot published
    RS peerNot published

    The exchange lists several addresses but not which go together: add one entry for each IPv4 and IPv6 pair.

  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18From its IX-F export and website members list
    IPv4195.66.228.130
    IPv62001:7f8:4::6:12d5:1
    Speed100000 Mbps (100G)
    RS peerNo

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