Michcom Limited: PeeringDB fix list
AS209049 · peeringdb.com/net/36876
5 things to fix in Michcom Limited's PeeringDB record, from what its exchanges publish: 4 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Michcom Limited'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 (4)
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:1690:0:3:3099:0:1 - In the entry with IPv4 196.49.90.39: set IPv6 to 2001:43f8:1690:0:3:3099:0: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 1G 10G - In the entry with IPv4 193.136.250.222: set Speed to 10000 (10G) (now 1000).
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 196.216.148.108: set Speed to 1000 (1G) (now 10000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 196.60.160.7: set Speed to 10000 (10G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Michcom Limited has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 196.60.12.40 IPv6 2001:7f8:b6:5:0:3:3099:1 Speed 1000 Mbps (1G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
From ixreport.com/net/209049/: 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.