Data center availability model
From Tier requirements to a complete colocation project
The Tier model helps compare power, cooling and maintenance paths. A dependable business service also requires a matching network, access policy, monitoring, security and support scope.
How to read data center Tier levels
Tier I
Basic infrastructure path
A single, non-redundant distribution path and basic capacity for non-critical workloads.
Tier II
Redundant capacity components
Additional capacity components reduce selected maintenance risks, while the distribution path remains limited.
Tier III
Concurrently maintainable
Planned work can be performed without shutting down the entire infrastructure path.
Tier IV
Fault-tolerant architecture
The model adds fault tolerance to concurrent maintainability for the most demanding environments.
Turn the requirements into a service
Choose the next step according to how much infrastructure you already own and how precisely the environment must be designed.
Tier and colocation FAQ
What does Tier III mean for a data center?
Tier III describes concurrently maintainable infrastructure. Planned maintenance can be performed without shutting down the entire facility path. Availability of a specific service is defined separately by its architecture, contract and SLA.
Does DataHouse claim Uptime Institute Tier certification?
No. DataHouse describes how its infrastructure aligns with Tier III assumptions, but this wording is not a claim of Uptime Institute certification. Exact technical and service parameters are confirmed in the contract and SLA.
How does the Tier level relate to server colocation?
The Tier level provides facility context. A colocation project still requires the right rack space, guaranteed power, connectivity, access rules, monitoring, backup and support scope.
What is the difference between Tier III and Tier IV?
Tier III focuses on concurrent maintainability, while Tier IV additionally assumes fault tolerance. The required level should follow workload risk, target SLA and the complete application architecture, not the label alone.