ixreport

LoCyan Network: PeeringDB fix list

AS204211 · peeringdb.com/net/40725

PeeringDB

2 things to fix in LoCyan Network's PeeringDB record, from what its exchanges publish: 1 to add, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.

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

  1. United Kingdom Kent Internet Exchange Point Kent, United Kingdom · PeeringDB 4316From its IX-F export
    IPv4185.0.24.207
    IPv62001:7f8:aa::207
    Speed10000 Mbps (10G)
    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

    IPv423.154.164.194
    IPv62602:f429:32::2
    Speed1000 Mbps (1G)

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