Gigastream plc: PeeringDB fix list

AS31712 · peeringdb.com/net/2160

PeeringDB

One thing to fix in Gigastream plc's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Gigastream plc'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 LONAP London, United Kingdom · PeeringDB 53
    ProblemPeeringDB hasThe export has
    IPv6 address in PeeringDB, not in the export2001:7f8:17::7be0:1none
    Port speed differs4G5G
    • In the entry with IPv4 5.57.80.80: set IPv6 to (empty) (now 2001:7f8:17::7be0:1); set Speed to 5000 (5G) (now 4000).

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