Quicktel: PeeringDB fix list
AS57945 · peeringdb.com/net/13546
One thing to fix in Quicktel's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-14 00:37 UTC.
Make the changes on Quicktel'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 IPv4 address in PeeringDB, not in the export 178.216.40.80 178.216.41.189 178.216.40.80 IPv6 address in PeeringDB, not in the export 2001:7f8:5b::80 2001:7f8:5b::458 2001:7f8:5b::80 Port speed differs 2 × 10G 10G - The entry with IPv4 178.216.41.189, IPv6 2001:7f8:5b::458 isn't in the export: delete it if that connection is gone.
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/57945/: 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.