A carrier-neutral data centre should give you a genuine choice of networks, cloud connections, and service partners rather than locking your colocation deployment into one provider. This checklist explains how to verify that claim, compare facilities consistently, and identify costs or operational limits before signing a contract.
Overview
Carrier neutrality is a practical purchasing question, not just a label. A facility may advertise multiple carriers while offering limited availability in your cabinet, expensive cross-connects, restricted meet-me-room access, or contract terms that make changing providers difficult. Your assessment should therefore cover both the building’s network ecosystem and the services available to your specific deployment.
Start by defining what you need over the contract term. Record your current bandwidth, expected growth, required cloud platforms, preferred network operators, latency-sensitive locations, IP address requirements, and any compliance or data-residency constraints. Then ask each colocation provider to answer the same questions in writing. Consistent questions make a data centre comparison more useful than a tour based on broad marketing claims.
Carrier neutrality also needs to be considered alongside power, security, resilience, and support. A well-connected facility may still be unsuitable if it cannot provide enough power density, has restrictive maintenance windows, or charges separately for routine operational work. For wider cost and control considerations, compare the options against colocation, dedicated server, and cloud hosting models.
| Area | What to verify | Evidence to request |
|---|---|---|
| Carrier choice | Which networks are available to your suite, cabinet, or floor? | Current carrier list, availability confirmation, and delivery conditions |
| Interconnection | How are cross-connects ordered, delivered, billed, and cancelled? | Price schedule, lead times, demarcation details, and terms |
| Cloud access | Are cloud on-ramps available directly or through partners? | Supported platforms, ports, handoff options, and recurring charges |
| Bandwidth | Can you buy transit, private connectivity, or diverse routes? | Commitment options, burst rules, service levels, and route information |
| Operations | Can staff support cabling, swaps, testing, and incident response? | Remote-hands menu, response targets, escalation process, and coverage hours |
| Physical capacity | Can the site support your cabinet footprint and equipment load? | Available space, power allocation, cooling approach, and expansion terms |
Checklist by scenario
When you need multiple internet carriers
- Ask for the complete list of carriers currently serving the facility, not only a list of companies that have a commercial relationship with the operator.
- Confirm that each preferred carrier can deliver service to your exact cabinet, cage, or suite.
- Ask whether diverse entrances, risers, pathways, and meet-me-room routes are available. “Carrier diversity” is less useful if all services share an unprotected physical path.
- Check whether the facility permits your own carrier contracts or requires you to purchase connectivity through the data centre.
- Request the normal installation process, expected handoff location, testing responsibility, and escalation path when a circuit fails.
When you need cloud on-ramps or hybrid connectivity
- Identify which cloud platforms and connectivity partners can be reached from the facility.
- Confirm whether the connection is delivered through a direct on-ramp, an exchange, a network partner, or a hosted connectivity service.
- Ask who owns the port, cross-connect, router, and fault investigation for each segment.
- Check whether cloud connectivity requires a minimum term, port size, additional cross-connects, or separate support contracts.
- Map the proposed connection against your application design, including backup paths and the location of dependent systems.
If your design combines private infrastructure with public cloud resources, use this hybrid cloud hosting deployment checklist to review dependencies before committing to a facility.
When you need predictable costs
- Separate one-time charges from monthly recurring charges for cross-connects, installation, ports, bandwidth, power, remote hands, and equipment delivery.
- Ask whether cross-connect pricing changes by carrier, media type, meet-me room, or connection length.
- Confirm billing increments for remote hands and whether after-hours or emergency work is charged differently.
- Check for minimum bandwidth commitments, overage rules, traffic measurement methods, and cancellation fees.
- Request a sample invoice or a written cost model using your proposed cabinet, power draw, and connectivity design.
When you need operational flexibility
- Confirm whether you can add a second carrier, move between cabinets, or increase power without renegotiating the entire agreement.
- Ask how quickly remote hands can access equipment and whether staff can perform cable tracing, rebooting, component replacement, and visual checks.
- Review visitor access, delivery procedures, escort requirements, camera coverage, and equipment removal controls.
- Ask how planned maintenance is announced, approved, and documented, including work that affects shared power, cooling, network pathways, or building access.
- Check whether you can install your own switching, routing, monitoring, and out-of-band management equipment.
What to double-check
Do not treat a carrier list as proof of current service availability. A carrier may be present in the building but unable to serve your rack, may require a new build, or may not offer the product you need at that location. Obtain a written availability check from both the facility and the proposed network provider.
Examine the meet-me room arrangement carefully. Ask where carrier equipment terminates, who controls access, whether internal cabling is managed by the facility, and how route diversity is documented. If resilience matters, request a simple path diagram showing entry points, rooms, risers, and cabinet handoffs. Avoid assuming that two circuits are diverse merely because they have different carrier names.
Review the cross-connect process from order to removal. Confirm the connector type, cable ownership, labelling standard, testing procedure, fault responsibility, and expected delivery time. Ask whether you can use your own structured-cabling contractor or must use the facility’s approved team.
Read the contract for limitations that can undermine neutrality. Look for preferred-provider clauses, exclusivity language, restrictions on direct carrier relationships, minimum terms, automatic renewal, price-change rights, access windows, equipment removal rules, and termination charges. Also compare the uptime definitions and exclusions in the service agreement using this guide to reading a hosting uptime SLA.
Finally, verify capacity rather than accepting a general statement that the site supports high-density equipment. Ask for your usable power allocation, permitted circuit types, rack dimensions, cooling limits, expansion process, and any restrictions on batteries, storage systems, or specialist equipment.
Common mistakes
- Confusing presence with choice: A building with many logos may not support the exact circuits, routes, or commercial terms you require.
- Comparing headline rent only: Cross-connects, power, remote hands, installation, bandwidth, and access charges can materially change the total cost.
- Ignoring physical diversity: Separate providers do not automatically mean separate entrances, ducts, risers, or meet-me rooms.
- Leaving cloud connectivity until later: On-ramps and private connections may have separate ordering processes and lead times.
- Accepting verbal assurances: Put availability, support targets, maintenance procedures, and expansion rights into the proposal or contract.
- Skipping an operational visit: A polished sales tour does not replace checks of loading access, security procedures, remote-hands workflow, and equipment routes.
- Forgetting the exit plan: Confirm how circuits, cross-connects, hardware, IP assignments, and data will be disconnected or migrated. The data centre exit strategy checklist can help structure this review.
When to revisit
Recheck this assessment before signing, renewing, or materially expanding a colocation agreement. Carrier availability, cloud interconnection products, cross-connect pricing, certifications, remote-hands terms, and facility capacity can change even when your cabinet remains in place.
For an existing deployment, review the checklist at least during each annual vendor assessment and before seasonal capacity planning. Revisit it sooner after a network incident, a major application migration, a new compliance requirement, an acquisition, or a change in traffic patterns. Repeat the review whenever the facility announces a new carrier, connectivity product, power expansion, maintenance programme, or contract update.
Use a simple evidence register with five columns: requirement, provider response, supporting document, owner, and review date. Mark each item as confirmed, conditional, or unresolved. Before selecting a facility, resolve every item that could affect resilience, cost, access, or your ability to change connectivity providers. Then keep the register with your infrastructure documentation and update it whenever your network design or the data centre’s service catalogue changes.
