Summary

  • On 10 November 2026 the MIX front page carried three counters — 469 ASN, a 3890 Gb/s peak, 24.02 Tb/s of capacity — and dated none of them, so every figure in this article is quoted as displayed that day rather than as a measurement of a stated period.
  • The same page names six IX platforms and fourteen buildings, then leaves the two lists unjoined: nothing on it says which platform sits in which room, which networks are reachable at a given handoff, or whether one order reaches past a single site. For anyone deciding whether to connect, that gap matters more than the headline numbers.

Start with the address, because it is the only precise thing on the page. MIX S.r.l. is registered at Via Caldera 21, Building Orange/3, 20153 Milan. That is a company address. It is not a description of a network, and the rest of the page does not close the distance between the two.

What the page does instead is list. Six platforms appear under the heading of an IX platform: MIX Milano, MIX Palermo, MIX Bologna, MIX Roma, MIX Caserta, MIX Salonicco. Fourteen names appear under a separate heading of locations: MIX Core DC, Equinix ML2, Avalon Campus, C21, Vaultica Data Center MIL01, Data 4 MIL1, Mediterra PMO 01, Aruba IT3, Equinix ML5, Balkan Gate Thessaloniki, BOIX, Mediterra ROM 01, Aruba IT4, Data Felix.

Read that second list as a guest list of the Italian hosting industry and it is striking. Equinix appears twice, Aruba twice, Mediterra twice, alongside Data 4, Vaultica, Avalon Campus, C21 and Data Felix. Two entries are other exchanges' brands: BOIX and Balkan Gate Thessaloniki. One name, MIX Core DC, carries the company's own mark. Those are labels on a page, not title deeds, and the retained text says nothing about who owns the building, who holds the lease or who signs the cross-connect order. But the naming is not neutral either.

An exchange that markets reach out of rooms carrying other operators' names is telling you something about where its capital sits.

Here is where I stop reporting and start arguing, and the difference should be visible on the page. My reading is that MIX presents a service footprint wider than the space it controls, and that a large part of what it sells is presence — a handoff inside a room a counterparty already occupies — rather than a road between cities. The page cannot prove that. It also cannot be read to prove the opposite: whether MIX owns, leases or leaves inter-city capacity to its customers is simply not disclosed in the material I retained.

What the page does support is the narrower observation that its own buildings and its platform brands are listed as two sets, not one map.

That missing map is the practical problem. A network engineer choosing a handoff needs to know which of the six platforms terminates at the building in question, which peers are present there, and how many of the 469 connected ASNs are actually reachable from that port. The published counter is network-wide and undated. It is not 469 peers at every site, not 469 distinct companies, and not a promise that a port in Caserta reaches Palermo without somebody buying transport in between. An operator can plan an interconnection budget on the first reading and discover the second at the cross-connect desk.

The two traffic numbers deserve the same discipline, because they invite a misuse the page does nothing to correct. A peak of 3890 Gb/s sits against published capacity of 24.02 Tb/s, roughly one-sixth (MIX). That is a ratio between two figures the operator publishes. It is not port utilisation, it is not the share of capacity sold, and it is not evidence of spare headroom anywhere in particular; without a per-platform breakdown the average belongs to nothing a buyer can point at. The temptation to read it as an efficiency verdict is strong and should be resisted by anyone who has ever argued about what a capacity number means.

MIX S.r.l. - Milan Internet eXchange also has a documented operational history in this publication. In August 2026 we covered its statement on peering-LAN resilience, which treated the loss of an IX path as something a prepared operator absorbs through over-provisioned transit and diversified peering, and treated frequent reconvergence as an operational risk in its own right. That is prior coverage of a different question: whether the fabric behaves when it breaks. This article asks what the fabric is as a commercial object, and the answer to that question is not on the resilience page either.

For a reader deciding whether to connect, the useful output of all this is a short interrogation list rather than a verdict. Ask which platforms the chosen building serves. Ask whether one membership or service order entitles you to reach the other five, and if so under what obligation. Ask who supplies any transport between them and whose name appears on that invoice. Ask which additional charges — facility cross-connect, installation, recurring access — sit outside the exchange fee. Ask who answers the phone at three in the morning when the path between two of those rooms goes dark. None of those questions is answered by a count of 469.

What can be said plainly is this. MIX publishes a wide footprint, a modest peak against a much larger installed capacity, and a network count without a date. It publishes the rooms and the platforms. It does not publish the wiring between them, and until it does, the number a buyer should trust least is the biggest one on the page.

The company itself sits at one address in Milan. Its page claims fourteen buildings and six cities, and the interesting tension is that both statements can be true at once. https://btw.media/en/directory/mix-s-r-l-milan-internet-exchange-it