LinkSecured Networks: PeeringDB fix list

AS19740 · peeringdb.com/net/1716

PeeringDB

2 things to fix in LinkSecured Networks's PeeringDB record, from what its exchanges publish: 2 to check. As of 2026-10-08 20:58 UTC.

Make the changes on LinkSecured Networks'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 LinkSecured Networks 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 Any2West Los Angeles and Silicon Valley, United States · PeeringDB 142Not on its website members list
    IPv4206.72.210.135
    IPv62001:504:13::210:135
    Speed10000 Mbps (10G)

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

  2. United States NYIIX Los Angeles Los Angeles, United States · PeeringDB 23Not on its website members list
    IPv4149.112.104.75
    IPv62001:504:a::a501:9740:1
    Speed10000 Mbps (10G)

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

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