LambdaNetUA: PeeringDB fix list
AS25526 · peeringdb.com/net/36920
One thing to fix in LambdaNetUA's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 18:53 UTC.
Make the changes on LambdaNetUA'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 LambdaNetUA's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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/25526/: 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.