ixreport

Htroy Network Research Limited: PeeringDB fix list

AS139216 · peeringdb.com/net/20186

PeeringDB

4 things to fix in Htroy Network Research Limited's PeeringDB record, from what its exchanges publish: 3 to add, 1 at exchanges that look shut down. As of 2026-10-08 22:13 UTC.

Make the changes on Htroy Network Research Limited'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 Htroy Network Research Limited's PeeringDB record. Add one entry per connection with these values.

  1. Switzerland 4b42 Internet Exchange Point Zurich, Switzerland · PeeringDB 2447From its IX-F export and website members list
    IPv4185.1.125.161
    IPv62001:7f8:d0::2:1fd0:1
    SpeedNot published
    RS peerYes
  2. United States EVIX Fremont, United States · PeeringDB 2274From its IX-F export and website members list
    IPv4–
    IPv62602:fed2:fff:ffff:6::106
    Speed1000 Mbps (1G)
    RS peerYes

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

  3. Germany KleyReX Frankfurt, Germany · PeeringDB 123From its IX-F export and website members list
    IPv4–
    IPv62001:7f8:33::a113:9216:1
    Speed100 Mbps (100M)
    RS peerYes

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

Exchanges that look shut down (1)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Only one outside network

    IPv4–
    IPv62402:e380:142:1::4
    Speed30 Mbps (30M)

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