What Colocation Actually Costs When You Read the Fine Print

The quote looked great. A clean per-rack rate, reasonable power allocation, maybe a note about "redundant connectivity." You sign, you ship your hardware, and three months later the invoice is 40% higher than what you budgeted. Sound familiar?

This happens constantly in colocation. Not because providers are necessarily dishonest — though some are — but because the industry has developed a pricing language designed to look simple while hiding the variables that actually drive your bill. If you've never run a data center or operated network infrastructure yourself, it's easy to miss. If you have, you know exactly which line items to interrogate before you sign anything.

Let me walk through what colocation actually costs when you get past the rack rate.

The Rack Rate Is Just the Starting Point

Every colocation provider leads with a rack rate. It's the number in the sales deck, the number on the comparison spreadsheet, the number that gets approved in your budget meeting. It's also almost never what you pay.

The rack rate covers physical space. That's it. What it doesn't cover — or covers only up to a threshold that's easy to exceed — is everything that makes that space actually useful.

Power is where most people get surprised first. Providers quote power in kilowatts, but how they measure and bill it varies significantly. Some bill on committed power (you pay for what you reserved whether you use it or not). Some bill on metered usage. Some do both — a base commitment plus overage charges if you spike. A rack of dense compute hardware running hot workloads can draw 8-10kW or more. If your contract committed to 5kW and your actual draw runs 7kW, you're paying overage rates on that delta every month, at rates that can be two to three times the base power cost.

Before you sign anything, get the actual per-kW rate for both committed and metered power. Then model your realistic power draw, not the theoretical minimum.

Cross-connects are the second place budgets blow up. A cross-connect is the physical cable that connects your equipment to a network provider, another tenant, or the facility's shared infrastructure. They sound like a minor detail. They're not. Cross-connect fees typically run $50–$300/month per connection, and you might need several — one for your primary transit provider, one for a backup, one for out-of-band management access. Some facilities charge installation fees on top of the monthly recurring cost. If you're planning to connect to multiple carriers for redundancy, price out every cross-connect before you commit to a facility.

Remote Hands: The Line Item Nobody Budgets For

You can't always fly to your data center. That's partly the point of colocation — your hardware lives somewhere with better power, cooling, and connectivity than your office. But when something needs a physical intervention, you need someone on-site to do it.

That's remote hands. And it's almost universally billed in a way that punishes you for using it.

Standard remote hands rates at most facilities run $75–$200 per hour, often with a one-hour minimum. After-hours rates — which at most places means anything outside a narrow weekday window — can be 1.5x to 2x the standard rate. Some facilities charge a dispatch fee just to have a technician walk to your cage, before any billable time starts.

Think about what that means in practice. You have a server that needs a hard reboot at 11pm on a Saturday. You call the facility. They dispatch someone. You pay a dispatch fee, a one-hour minimum at after-hours rates, and maybe a "priority response" surcharge if you need it done in under 30 minutes. That single incident can cost $400–$600.

This isn't hypothetical. If you're running production infrastructure in a colo facility, you will eventually need remote hands at an inconvenient time. Budget for it explicitly, and ask providers exactly how they structure those charges — including what counts as "after hours" and whether there are any included hours in your base contract.

Bandwidth: The Egress Problem, Colo Edition

You probably already know about AWS egress fees. The colo version is subtler but equally real.

Most colocation providers offer "blended" or "burstable" bandwidth — you get a committed data rate (say, 1Gbps), and you can burst above that, billed at a per-Mbps rate for the overage. The 95th percentile billing model is standard: they throw out your top 5% of usage samples and bill you on the next highest point. That's actually reasonably fair for bursty workloads.

What's less fair is when providers advertise "included bandwidth" that's technically unlimited but practically constrained by a port speed that's too small for your actual traffic, forcing you to upgrade to a higher-tier circuit at a significant price jump. Or when the "included" bandwidth is on a shared, oversubscribed segment that degrades during peak hours — and dedicated capacity costs extra.

Ask specifically: What is the port speed? Is it shared or dedicated? What's the 95th percentile billing rate for overage? Is there a minimum commit on bandwidth separate from the rack commit? What's the actual SLA on throughput, not just uptime?

If a provider can't answer those questions clearly, that tells you something.

Contract Terms That Cost You Later

The monthly rate is only part of the cost equation. Contract structure matters too, and some terms that look neutral can be expensive in practice.

Minimum terms are usually 12–36 months. That's not inherently unreasonable — facilities have real capital costs and need predictable revenue. But what happens if you need to scale down or exit early? Early termination fees can be substantial, sometimes the full remaining contract value. If your business is growing or changing, flexibility has real economic value. Price it accordingly when you're comparing options.

Auto-renewal clauses are common and often have short cancellation windows — sometimes 60–90 days before the renewal date. Miss that window and you're locked in for another full term. Put a calendar reminder the day you sign.

Power rate escalation is less common but worth checking. Some contracts allow the provider to pass through utility rate increases. In a region with volatile power costs, that can move your bill meaningfully over a multi-year term.

SLA credits look good on paper but often have caps and exclusions that make them nearly worthless. A 10% monthly credit for a 4-hour outage sounds like accountability. When your outage costs you $50K in lost revenue and the credit is $300, it's not. Read the SLA section carefully, especially the exclusions.

What TCO Actually Looks Like

Let me put some numbers on this. A realistic colocation deployment for a mid-sized company — say, 2 full racks of compute and storage hardware — might look like this when you build out the actual TCO:

Line Item	Quoted/Assumed	Realistic Monthly
Rack rate (2 racks)	$800/rack	$1,600
Power (metered, actual draw)	"included to 4kW"	$400–$600
Cross-connects (3)	Not mentioned	$450
Remote hands (avg 2–3 incidents/mo)	Not mentioned	$300–$500
Bandwidth overage	"unlikely"	$200–$400
Total	$1,600	$2,950–$3,550

That's roughly double the quoted rate. Not unusual. And it doesn't include the one-time costs: cage setup fees, initial cross-connect installation, shipping your hardware, and the engineer time to rack and cable everything if you're not doing it yourself.

The point isn't that colocation is a bad deal — for the right workloads, it absolutely isn't. The point is that you need to model the full number, not the rack rate.

How to Actually Compare Providers

When you're evaluating colocation options, here's the checklist that matters:

• Get a fully-loaded quote that includes power at your expected draw, all cross-connects you'll need, and remote hands at your expected usage rate
• Ask for the after-hours remote hands rate specifically
• Confirm port speed, whether it's shared or dedicated, and the overage billing model
• Read the SLA section, not just the uptime number — focus on the exclusions and credit caps
• Check the auto-renewal and early termination terms
• Ask whether power rate increases can be passed through during the contract term

If a provider won't give you clear answers on any of these, that's your answer.

At IDACORE, we price colocation with flat, predictable rates and we'll walk you through exactly what your full monthly cost looks like before you commit — including power, connectivity, and what remote hands actually costs when you need it. Our team has been operating network infrastructure in the Pacific Northwest for 30 years, which means we've seen every way a colo contract can surprise you, and we'd rather you know upfront. If you're evaluating colocation options in Idaho and want a straight answer on what it actually costs, get a real quote from our team.