Altecom: PeeringDB fix list
AS16030 · peeringdb.com/net/834
3 things to fix in Altecom's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Altecom'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 (2)
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 Port speed differs 10G 1G - In the entry with IPv4 185.1.119.17: set Speed to 1000 (1G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 10G 1G - In the entry with IPv4 185.1.192.7: set Speed to 1000 (1G) (now 10000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Altecom has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 193.242.98.4 IPv6 2001:7f8:2a:0:1:1:1:6030 Speed 10000 Mbps (10G)
From ixreport.com/net/16030/: 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.