Six Degrees - Datahop: PeeringDB fix list

AS6908 · peeringdb.com/net/837

PeeringDB

3 things to fix in Six Degrees - Datahop's PeeringDB record, from what its exchanges publish: 1 to add, 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on Six Degrees - Datahop'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 (1)

On the exchange's own member list, but not in Six Degrees - Datahop's PeeringDB record. Add one entry per connection with these values.

  1. United States DE-CIX New York New York, United States · PeeringDB 804From its IX-F export and website members list
    IPv4206.82.104.13
    IPv62001:504:36::1afc:0:1
    Speed10000 Mbps (10G)
    RS peerYes

Check these entries (2)

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

  1. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18Not on its IX-F export or website members list
    IPv4195.66.225.32
    IPv62001:7f8:4::1afc:1
    Speed30000 Mbps (30G)
  2. United Kingdom LINX Manchester Manchester, United Kingdom · PeeringDB 583Not on its IX-F export or website members list
    IPv4195.66.244.13
    IPv62001:7f8:4:2::1afc:1
    Speed10000 Mbps (10G)

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