Thales UK: PeeringDB fix list
AS48688 · peeringdb.com/net/35583
One thing to fix in Thales UK's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Thales UK'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.
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4::be30:1 2001:7f8:4::be30:2 Port speed differs 2 × 5G 4 × 5G - In the entry with IPv4 195.66.231.120: set IPv6 to 2001:7f8:4::be30:1 (now empty).
- In the entry with IPv4 195.66.231.121: set IPv6 to 2001:7f8:4::be30:2 (now empty).
From ixreport.com/net/48688/: 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.