What carrier-neutral actually means
A carrier-neutral colocation operator does not own a transit network and does not insert its own network between the tenant and the carriers in the building. Tenants pick their carriers and cross-connect to them. The operator's role is space, power, cooling, and the meet-me room that connects tenants to carriers. Most independent colocation operators are carrier-neutral in this sense, and PeeringDB registers carrier-neutral facilities as such.
The opposite end of the spectrum is a single-carrier facility where the operator is the carrier or wholly owned by one. The operator's commercial alignment is with that carrier, which often means tenants get preferential pricing on that carrier's transit and may face friction when adding others. There is a middle case where a carrier owns multiple buildings and runs some as carrier-neutral, some as carrier-owned. Read each facility on its own.
When carrier-neutral is the right pick
Workloads that benefit from carrier neutrality typically have one or more of these characteristics. Diverse traffic destinations where no single carrier has the best path to all of them. A multi-year horizon during which the carrier mix may change. Compliance or contractual requirements for transit redundancy across two independent carriers. Negotiating leverage that comes from being able to switch carriers without moving the cage.
For most enterprise IT and most cloud-adjacent workloads, the answer is carrier-neutral. For most regulated workloads, the redundancy requirement makes carrier-neutral the only viable answer.
When single-carrier or carrier-owned is the right pick
Single-carrier facilities can be the better answer when the workload commits traffic predominantly to one carrier anyway and that carrier's facility has the best price and operational integration. Telco-grade workloads inside a Tier 1 carrier's own facility often get better SLAs and lower cross-connect costs than the same workload in a third-party carrier-neutral building. Carriers also sometimes operate facilities in metros where no carrier-neutral alternative exists; in that case the procurement decision is not actually between two options.
How to read the operator's network footprint
The two signals worth checking before contract are the operator's PeeringDB facility record (which lists carriers and exchanges present, plus the carrier-neutral status) and the operator's own network presence on viabandwidth. A direct operator with a verified own network footprint is structurally different from a colocation operator that resells space without running its own network.
On viabandwidth, the operator profile shows the operator type (direct, carrier-neutral, marketplace, or reseller) and the network presence (announced prefixes, internet exchange count) where the operator runs its own infrastructure. Direct operators with high exchange presence are typically also carrier-neutral; carriers that operate colocation as a service almost always run carrier-owned facilities. Always confirm independently, since the labels and the contract may differ.
Contract clauses that operationalize neutrality
Marketing-page neutrality means nothing unless it survives the contract. The clauses worth asking for are a commitment that the operator will not refuse a cross-connect to any carrier present in the building, a cross-connect price schedule that is the same across all carriers in the building, and a non-discrimination clause covering meet-me room access. Operators that resist these clauses are signalling that the neutrality on the marketing page has limits.
Shortlist workflow
For most procurement decisions, the workflow is to filter the country hub on viabandwidth to the metro that fits the latency and jurisdiction requirements, identify operators tagged carrier-neutral, cross-check each operator's PeeringDB record for the carriers you actually need, and unlock the operator dossier for the operators on the shortlist to get the verified contact route. Decide between carrier-neutral and carrier-owned only when the procurement profile makes the carrier-owned case (heavily one-carrier workload, no alternative in the metro, better operational integration).