MEDIANET INVEST M.I.K.E: PeeringDB fix list
AS200736 · peeringdb.com/net/17687
4 things to fix in MEDIANET INVEST M.I.K.E's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on MEDIANET INVEST M.I.K.E'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 (2)
On the exchange's own member list, but not in MEDIANET INVEST M.I.K.E's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.226.249 IPv6 2001:67c:29f0::20:736:1 Speed Not published RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
IPv4 194.93.123.121 IPv6 2001:7f8:37:21:2347:20:736:1 Speed 100000 Mbps (100G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
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 30G 100G - In the entry with IPv4 178.18.237.59: set Speed to 100000 (100G) (now 30000).
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 20G 100G - In the entry with IPv4 217.29.67.139: set Speed to 100000 (100G) (now 20000).
From ixreport.com/net/200736/: 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.