Colocation Connectivity & Cross-Connects
Connectivity is often the deciding factor in colocation selection—and the hidden cost driver in your monthly bill. A facility with cheaper space pricing but limited carrier diversity and expensive cross-connects can cost more than a higher-priced building with dense, affordable interconnect. This guide explains carrier presence, cloud on-ramps, cross-connect economics, and what to verify before signing.
Carrier-neutral vs carrier-specific facilities
Carrier-neutral facilities allow multiple network providers to physically terminate in the building, giving you competitive cross-connect pricing and carrier diversity. Carrier-specific facilities are operated by or tied to a single network provider—bundled connectivity may seem simpler, but it limits your interconnect options and negotiating leverage.
Most commercial buyers should prefer carrier-neutral facilities unless they have a specific reason to standardize on a single carrier. Carrier density at the building level—not metro level—is what matters.
Cloud on-ramps: what they are and why they matter
If your architecture is hybrid (colocation + cloud), verify that the cloud on-ramps you need are physically present in the building you are evaluating—not just in the metro. A building with AWS Direct Connect but no Azure ExpressRoute is not a fit if you need both.
For the buyer view, see how cloud on-ramps work in colocation.
- AWS Direct Connect: private connection to AWS regions, bypassing the public internet
- Azure ExpressRoute: private connection to Microsoft Azure
- Google Cloud Interconnect: private connection to Google Cloud Platform
- Oracle Cloud Network FastConnect: private connection to Oracle Cloud
- Cloud on-ramps reduce latency, increase bandwidth predictability, and eliminate egress fees vs public internet
Cross-connect economics: the hidden cost driver
With many cross-connects, interconnect charges can rival or exceed the space cost itself. Always model cross-connect costs into your TCO, not just space and power.
| Cost element | What to expect | What to ask |
|---|---|---|
| Cross-connect MRC | Ask the provider (per connection, monthly) | How many included? Per-connection cost? |
| Cross-connect NRC | Ask the provider (per connection, one-time) | Can NRC be waived or capped? |
| Lead time | Lead times vary by carrier and building; confirm with the provider. | What is the typical LOA-to-activation timeline? |
| Meet-me room access | Included or per-cross-connect | Is the MMR carrier-neutral and accessible? |
| Inter-building cross-connects | Ask the provider (per connection) | Are campus or inter-building connections needed? |
What to verify at the building level
A provider saying "we have 50+ carriers in the metro" is not useful if only 5 are physically in your building. Ask for the building-level carrier list and verify your required carriers are on it.
- Which carriers are physically terminated in this building (not just the metro)?
- Are the cloud on-ramps you need (AWS, Azure, GCP) present in this building?
- Is the meet-me room carrier-neutral with documented access procedures?
- What are cross-connect MRC, NRC, and typical lead times?
- Are there any restrictions on bringing in new carriers?
- Is dark fiber or wavelength service available to other buildings or campuses?
Scoring interconnect in your TCO comparison
Treat interconnect as a scored line item, not a qualitative checkbox. For each provider, list the carriers and cloud on-ramps present at the building level, model the cross-connect MRC and NRC for your expected connection count, and add it to the normalized cost per usable kW per month TCO. A lower space fee loses quickly if cross-connects are slow, expensive, or limited.
Related Guides
Ready to compare providers?
Get matched quotes from multiple facilities or talk through your requirements with an expert.