ixreport

COMPUTE: PeeringDB fix list

AS399670 · peeringdb.com/net/43799

PeeringDB

One thing to fix in COMPUTE's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-11 06:39 UTC.

Make the changes on COMPUTE'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 COMPUTE'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.167
    IPv62001:7f8:aa::167
    Speed10000 Mbps (10G)
    RS peerNo

    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/399670/: 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.