Sierra Communications: PeeringDB fix list
AS154031 · peeringdb.com/net/39772
One thing to fix in Sierra Communications's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Sierra Communications'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 differs 103.121.64.63 163.223.201.63 IPv6 address differs 2400:efa0::15:4031:1 2001:df0:a940::15:4031:1 Port speed differs 10G 25G - In the entry with IPv4 103.121.64.63: set IPv4 to 163.223.201.63 (now 103.121.64.63); set IPv6 to 2001:df0:a940::15:4031:1 (now 2400:efa0::15:4031:1); set Speed to 25000 (25G) (now 10000).
From ixreport.com/net/154031/: 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.