Lepida AS205139: PeeringDB fix list
AS205139 · peeringdb.com/net/18473
4 things to fix in Lepida AS205139's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Lepida AS205139'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 Lepida AS205139's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.231.33 IPv6 2001:7f8:101:13::33 Speed 40000 Mbps (40G) RS peer Yes
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 2001:7f8:b:100:1d1:a520:5139:61 Port speed differs 10G 100G - In the entry with IPv4 217.29.67.61: set IPv6 to 2001:7f8:b:100:1d1:a520:5139:61 (now empty); set Speed to 100000 (100G) (now 10000).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:23:ffff::177 - In the entry with IPv4 194.116.96.177: set IPv6 to 2001:7f8:23:ffff::177 (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 1G 100G - In the entry with IPv4 185.1.115.65: set Speed to 100000 (100G) (now 1000).
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/205139/: 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.