LAMBDA: PeeringDB fix list
AS150942 · peeringdb.com/net/36600
3 things to fix in LAMBDA's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on LAMBDA'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 (3)
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 2401:91e0:31::150:942:1 - In the entry with IPv4 43.254.82.90: set IPv6 to 2401:91e0:31::150:942:1 (now empty).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 20G 10G - In the entry with IPv4 123.108.11.23: set Speed to 10000 (10G) (now 20000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 119.11.186.177: set Speed to 1000 (1G) (now 10000).
From ixreport.com/net/150942/: 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.