M-Networks Sp. z o.o.: PeeringDB fix list
AS198611 · peeringdb.com/net/11006
2 things to fix in M-Networks Sp. z o.o.'s PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 22:13 UTC.
Make the changes on M-Networks Sp. z o.o.'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:7f8:60::19:8611:1 - Add an entry: IPv4 –, IPv6 2001:7f8:60::19:8611:1, speed 1000 (1G).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If M-Networks Sp. z o.o. has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 178.216.40.141 IPv6 2001:7f8:5b::141 Speed 10000 Mbps (10G) IPv4 178.216.40.180 IPv6 2001:7f8:5b::180 Speed 10000 Mbps (10G)
From ixreport.com/net/198611/: 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.