ixreport

SharpStream: PeeringDB fix list

AS58188 · peeringdb.com/net/28427

PeeringDB

One thing to fix in SharpStream's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on SharpStream'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 (1)

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
    IPv4 address missing from PeeringDB195.66.224.42195.66.224.42 195.66.228.131
    IPv6 address missing from PeeringDB2001:7f8:4::1502:32001:7f8:4::1502:3 2001:7f8:4::e34c:1
    Port speed differs10G100G + 10G
    • Add an entry: IPv4 195.66.228.131, IPv6 2001:7f8:4::e34c:1, speed 100000 (100G), RS peer yes.

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