Telcom Networks: PeeringDB fix list
AS31631 · peeringdb.com/net/8678
2 things to fix in Telcom Networks's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Telcom Networks'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 Telcom Networks's PeeringDB record. Add one entry per connection with these values.
-
IXLeeds Leeds / Western Yorkshire, United Kingdom · PeeringDB 435From its IX-F export and website members listIPv4 91.217.231.49 IPv6 2001:7f8:67::7b8f:1 Speed Not published RS peer Not published
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 Address belongs to another network in PeeringDB 91.217.231.49 is AS5631 Elevate UK 91.217.231.49 An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
From ixreport.com/net/31631/: 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.