Physical site risk rarely gets the scrutiny it deserves during procurement, even though a facility’s location says as much about resilience as its redundancy rating does.
There is a quiet shift happening in how organisations think about where their infrastructure lives. What was once a purely technical decision now sits squarely on the boardroom agenda, and for good reason.
Why it matters now
The market has split in two. Standard enterprise workloads still run comfortably at three to five kilowatts a rack, while accelerated-compute deployments are pushing twenty, fifty, even a hundred kilowatts. Those two worlds are priced and provisioned very differently, and conflating them is a common and expensive mistake.
Power has overtaken floor space as the binding constraint in most primary markets. Vacancy rates have fallen to record lows, and the practical effect is that capacity — particularly high-density capacity — increasingly needs to be reserved well ahead of when you actually need it.
What good looks like in practice
The strongest operators are transparent by default — uptime history, incident reports, and maintenance schedules are available without a special request. That openness is itself a signal worth weighing.
Good facilities make the boring things boring: predictable billing, clear escalation paths, and remote-hands requests that get done on the timeline promised, not the timeline hoped for.
The factors that actually move the needle
Tier classification tells you what a facility was designed to do, not how well it is run. A well-operated Tier III site routinely outperforms a poorly managed Tier IV one on the metric that matters: real-world availability.
Headline pricing is the least reliable basis for comparison. Two facilities quoting similar rates can differ enormously once you account for power redundancy, cross-connect fees, remote-hands rates, and the small print around escalations and renewals.
A practical way to evaluate
Model the whole cost, not the monthly line. Setup fees, cross-connects, bandwidth, growth headroom, and exit terms all belong in the comparison. The cheapest rack rate is rarely the cheapest deployment.
Start with requirements, not providers. Pin down your power per rack, total committed capacity, connectivity needs, and the compliance regimes you answer to. That single page of clarity will shape every conversation that follows.
A short checklist before you sign
- Ask for real uptime history, not just the design tier
- Total the full cost of ownership, including the fees that hide in the small print
- Leave headroom for growth, including higher-density racks down the line
- Map the network ecosystem: carriers, internet exchanges, and cloud on-ramps
- Clarify remote-hands response times and what is included versus billed separately
The bottom line
The teams that get this right are rarely the ones with the most resources — they are the ones who asked better questions earlier in the process.