The Uptime Institute’s Tier I–IV framework is not a quality ranking. It is a structured way of describing what happens when a component fails, and what kind of maintenance you can do without taking the load down. In procurement, that turns into a filter: facilities either meet the tier you need or they do not. The harder question — the one we actually ask buyers — is whether the tier they have written down is the tier their workload requires.
What the four tiers describe
The framework is cumulative. Each higher tier inherits everything below it and adds a property.
- Tier I — single non-redundant distribution path. Roughly 99.671% availability, ~28.8 hours of expected annual downtime. Maintenance takes the load down. Suitable for non-critical workloads, edge, internal-only services.
- Tier II — adds redundant components on a single distribution path. ~99.749% availability, ~22 hours expected annual downtime. Component failure is survivable; planned maintenance still requires downtime.
- Tier III — adds concurrent maintainability. Multiple distribution paths, only one active at a time. ~99.982% availability, ~1.6 hours of expected annual downtime. You can take any component or path offline for maintenance without taking the load down. Most enterprise procurement defaults here.
- Tier IV — adds full fault tolerance. Multiple active distribution paths, every component independently redundant. ~99.995% availability, under 26 minutes of expected annual downtime. Built for workloads where a single fault must not be visible.
The numbers are expected annual downtime under the framework, not contractual SLAs. Provider SLAs are a separate thing — usually written tighter than the tier suggests, and usually with caveats that matter.
When the answer is “lower than you wrote down”
The most common mistake we see in RFPs is over-specifying tier. Three patterns:
Backup workloads at Tier III. Cold storage and backup do not need 99.982%. Tier II with sensible operational practice is almost always the right answer. The cost difference, over a five-year term, is real money.
Fault-tolerant AI at Tier III. Modern training workloads are typically run on framework-managed clusters that already tolerate node failure. If your maintenance windows can absorb planned downtime, Tier II + N+1 cooling at high power density usually beats Tier III + standard cooling, both on price and on sourcing options. We will say this even when the procurement memo has been pre-written.
Public-facing Tier IV. Tier IV is rarely the cheapest path to the availability target. Multi-region Tier III with proper failover is often more available, more flexible, and less expensive than a single Tier IV facility. The Tier IV option remains relevant for specific regulated or sovereign workloads where geographic redundancy is not contractually acceptable.
When the answer is “higher than you wrote down”
Less common, but worth flagging. Buyers running healthcare, real-time payments, or trading workloads sometimes spec Tier II “to start”. The conversion to Tier III later is rarely free — it usually requires moving facilities. We push back on this at the intake stage and ask the procurement lead to talk to the operations lead before the brief leaves the building.
How the tier filter shows up in the RFQ
When you submit through our requirements wizard or RFQ form, tier becomes a hard filter on the shortlist. Facilities that cannot evidence the tier — through documentation, audit reports, or operational record — do not appear. We will sometimes propose one tier lower if the buyer’s underlying availability target permits it, with the reasoning written down. We will never propose one tier higher without flagging the additional cost.
There is no certification body that certifies tier compliance for an entire facility post-build. There is the Uptime Institute’s Tier Certification of Constructed Facility (TCCF), which is the version that matters for procurement. We treat TCCF as load-bearing evidence and fall back on operator-attested documentation only when the workload’s risk profile genuinely permits it.