A cross-connect is the physical link between customer equipment and a carrier, cloud on-ramp or another tenant inside an interconnection ecosystem. A rack quotation may exclude it completely.
Rather than quote one national average, this guide sets out the components to request and how to compare physically equivalent links across facilities.
What to include in the decision
- Separate cross-connect, port and bandwidth
- Identify the entire physical route
- Budget one-time and recurring charges separately
- Test implementation and service responsibilities
Separate cross-connect, port and bandwidth
The physical cross-connect typically pays for a fiber or copper pathway and its administration. It is not necessarily a carrier’s transit service, a cloud port subscription or the traffic volume sent across the connection.
If one offer includes only a fiber pair and another includes optics, patching, a cloud exchange port and managed connectivity, monthly prices are not comparable. Normalize each service element.
Identify the entire physical route
Ask whether the connection runs within one data hall, between two rooms, across buildings or onto a metro network. Distance, intermediate panels, meet-me-room access, splice work and route diversity may each change scope and schedule.
A redundant design should verify two genuinely independent routes. Paying twice for two cross-connects does not necessarily provide diversity if both share ducts, racks, carriers or building entry points.
Budget one-time and recurring charges separately
Create a line for the nonrecurring installation charge (NRC), the monthly recurring charge (MRC), additional patching, site visits, optics, cross-campus charges and provider minimum terms.
For migrations, overlap old and new links during testing. The double-billing period and activation dates can be as important to a first-year budget as the advertised monthly fee.
Test implementation and service responsibilities
A complete order specifies A/Z endpoints, cable type, connector, handoff speed, ownership of transceivers, demarcation point and who opens trouble tickets. Missing endpoints often delay activation.
Confirm how long troubleshooting takes and whether a cross-connect SLA covers only the physical pathway rather than carrier latency or cloud availability.
Illustrative first-year link cost
Assume four links at a hypothetical $250 MRC each and four $400 NRCs. One year costs (4 × $250 × 12) + (4 × $400) = $13,600 before carrier ports, bandwidth, tax and any route-diversity premium. All amounts are invented solely to demonstrate the method.
Quote-comparison example: identical circuits or different products?
Suppose Facility A quotes a low monthly fiber cross-connect but requires a separate cloud-exchange port, off-campus extension and paid termination. Facility B quotes a larger package including one meet-me-room connection and two physically diverse paths. Their quoted cross-connect prices do not describe the same service.
Request a line-level bill of materials with A/Z endpoints, dark-fiber strands, port capacity, patch panel, optics, NRC, MRC and the number of billable months in the first year. For a 24-month business case include installation, overlap with the old facility and any disconnect fee.
Equinix’s public product documentation illustrates the importance of distinguishing standard, campus, diverse and extended cross-connects as well as services with only nonrecurring charges. It is an example of provider product taxonomy, not a market average.
A full first-year calculation rather than a headline rate
Assume two physical cross-connects at an entirely hypothetical $300/month each, with $600 installation per connection, and a separate network-exchange port at $1,200/month. First-year recurring charges are 12 × (2 × $300 + $1,200) = $21,600. Add $1,200 of installation charges and the first-year subtotal becomes $22,800, before bandwidth, remote hands, optics, taxes, disconnect charges or redundant path premiums.
That is why comparing a $300 “cross-connect” advertisement with an $1,800 all-in quote is misleading: one may quote a single physical circuit while the other includes a port or a routed service. Require separate fields for NRC (nonrecurring), MRC (monthly recurring), included services and site-specific exclusions.
For resiliency, ask whether two circuits share a meet-me room, cable tray or conduit. Two independently invoiced connections may still fail together. A truly diverse route should be supported by provider drawings and an explicit service boundary.
Line-item request for the colocation quote
| Line item | Unit of measure | Clarification needed |
|---|---|---|
| Physical cross-connect | Per fiber pair/circuit per month | A-end, Z-end, connector and route |
| Cloud or exchange port | Per port / bandwidth tier | Speed, committed port term, overage |
| Install / deinstall | One-time per circuit | Expedite, termination and patch-panel fees |
| Diverse path | Per second route | Evidence of physical separation |
| Carrier transport | Circuit / committed bandwidth | Who bills WAN and optics |
How to validate provider documentation
Equinix’s published cross-connect documentation distinguishes standard, campus, diverse and extended products, and identifies different recurring and installation charge structures. Treat that as a provider-specific illustration: it does not establish competitive market rates or guarantee available products at the selected building.
When comparing two facilities, normalize first-year cost and a 36-month committed term, including overlap during migration. A technically correct connection that misses migration dates can be more expensive than a slightly higher monthly fee.
Questions to ask before signing or building
- Does the quote include MRC, NRC, patching and meet-me-room charges?
- Are cloud exchange, optical transceivers and bandwidth separate?
- Are A and B routes physically independent end to end?
- How are install dates, renewals and disconnect fees handled?
Methodology: illustrative figures are deliberately separated from sourced claims. Utility rates, commercial charges and engineering performance must be validated against site documents. Publication date: October 19, 2026.
Technical and commercial reference
- Equinix: Cross-connect pricing and billing terms — provider example, not a market price index