Triton Digital: PeeringDB fix list

AS13360 · peeringdb.com/net/4807

PeeringDB

3 things to fix in Triton Digital's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

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

Correct these entries (3)

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 Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::3430:1
    • In the entry with IPv4 195.66.225.171: set IPv6 to 2001:7f8:4::3430:1 (now empty).
  2. United States LINX NoVA Ashburn, Reston, Manassas, United States · PeeringDB 777
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:31::3430:1
    • In the entry with IPv4 206.55.196.49: set IPv6 to 2001:504:31::3430:1 (now empty).
  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:13::a501:3360:1
    • In the entry with IPv4 193.239.117.188: set IPv6 to 2001:7f8:13::a501:3360:1 (now empty).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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