What Are Cross-Connects in a Data Center? Buyer Basics

What is a cross-connect?

A cross-connect is a physical cable—fiber or copper—inside a data center that links your cabinet, cage, or suite to another party or service in the facility. That destination may be a network carrier, cloud on-ramp, internet exchange, or another tenant. Cross-connects are how a colo deployment turns space and power into usable connectivity. Installation fees, recurring charges, and delivery times are facility-specific, so treat them as first-class line items in every quote comparison.

A cross-connect is not the same thing as bandwidth. The cross-connect is the physical path between demarcations. A carrier, cloud, or internet service is a separate commercial and technical service that may use that path. Your request should identify both the physical connection and the service expected to run over it.

How a cross-connect works

Your equipment connects to a designated demarcation point in your cabinet or cage. The facility’s cabling path runs from that demarcation to a meet-me room or other interconnection location, where it reaches a carrier, cloud provider, internet exchange, or another approved destination. The exact handoff varies by building and provider, so ask for the facility’s ordering and demarcation diagrams during diligence.

Fiber is common when the connection needs distance, capacity, or optical equipment. Copper may be appropriate for shorter, specific interfaces. The right medium depends on the service, port type, distance, and facility standards. Ask who supplies optics, patching, labeling, testing, and documentation, and whether the carrier or the data center performs each step.

Common use cases

Carrier handoff. A cross-connect can link your colo equipment to dedicated internet access, transport, wavelength, or another carrier service. The carrier’s service terms and the facility’s cross-connect terms should be reviewed together.

Cloud on-ramp. A tenant may use a cross-connect to reach a cloud provider’s connection point. Confirm the cloud region, port requirements, virtual circuit process, and whether the facility has the required cloud presence today.

Internet exchange or blended IP. A cross-connect can provide access to an internet exchange or another network service. Confirm membership, port, routing, and any separate service obligations.

Private tenant-to-tenant link. Two parties in the same facility may request a private physical connection, subject to authorization and security procedures.

Campus or multi-building extension. Some operators offer connections between buildings or campuses. Ask whether the path is physically diverse, who owns it, and what service level applies.

A growing use case is running cross-connects to cloud on-ramps for hybrid workloads.

What affects cost and lead time

Cross-connect economics commonly include a non-recurring installation charge and a recurring monthly charge, but the actual structure is provider-specific. Media type, distance, building design, carrier involvement, expedite requests, and who supplies materials can affect both price and schedule. Avoid using an unverified generic price or promised interval in a business case.

Clarify whether the recurring charge is billed by the facility, the carrier, or both. Confirm move, change, disconnect, and re-termination fees. Ask how a failed test is handled and whether the provider supplies test results. A “ready” carrier in a marketing list may still require port ordering, customer authorization, engineering, and physical installation.

Cross-connect questions for an RFP

Include the following in your request:

• Required carriers, cloud providers, exchanges, and destinations.
• Fiber or copper preference and interface requirements.
• The desired demarcation point and who owns each side of the handoff.
• Whether production needs two physically diverse paths or separate meet-me rooms.
• Who orders, installs, labels, tests, and documents the connection.
• Current installation lead time and any expedited process.
• Recurring and one-time charges, change fees, and disconnect terms.
• Access, escort, authorization, and maintenance procedures.
• The escalation path if the cross-connect or carrier handoff fails.

The colocation RFP checklist can help turn these into comparable provider questions.

Why carrier neutrality matters

A carrier-neutral facility can give a buyer more choice among network providers, but neutrality does not automatically guarantee a particular carrier, price, latency, or service quality. Verify the current on-net list, meet-me room access, cross-connect policy, and cloud presence for the specific site. Read What Is a Carrier-Neutral Data Center? when comparing facility models.

Market choice matters too. Buyers may start with Ashburn, New York, or Chicago when network density and cloud connectivity are priorities, but the correct market depends on latency, users, regulations, and available capacity. Do not assume every building in a market offers the same interconnection options.

Frequently Asked Questions