LEC Communications: PeeringDB fix list
AS328567 · peeringdb.com/net/27587
2 things to fix in LEC Communications's PeeringDB record, from what its exchanges publish: 1 to correct, 1 at exchanges that look shut down. As of 2026-10-08 18:53 UTC.
Make the changes on LEC 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 IPv6 address missing from PeeringDB none 2001:43f8:6d0::104 2001:43f8:6d0::10:170 - In the entry with IPv4 196.60.10.170: set IPv6 to 2001:43f8:6d0::10:170 (now empty).
- In the entry with IPv4 196.60.8.104: set IPv6 to 2001:43f8:6d0::104 (now empty).
PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
Exchanges that look shut down (1)
In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.
-
Only one outside network
IPv4 196.223.24.5 IPv6 – Speed 10000 Mbps (10G)
From ixreport.com/net/328567/: 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.