Coeur d'Alene, Idaho sits roughly 45 minutes from Spokane by I-90, on a different power grid and in a different state's regulatory jurisdiction than most Spokane-area production infrastructure. IDACORE North, at 2115 N Government Way, offers per-U and full cabinet colocation at $300/kW/month, open for active orders today — the same pricing model as IDACORE Boise, with none of the cross-border data residency questions.
Why Does Grid Separation Matter for DR?
Disaster recovery planning that puts your primary and backup sites on the same utility grid isn't disaster recovery. It's wishful thinking with a service contract attached. If a Spokane substation trips, or Avista has a regional event, and your "backup" site is fed by the same infrastructure, you've built redundancy that fails exactly when you need it.
IDACORE North runs on Idaho Power infrastructure, physically and administratively separate from the utilities serving Spokane. That's not a marketing distinction — it's the actual thing that determines whether your DR site stays up when your primary site doesn't. Same regional weather patterns, same general geography, genuinely different grid. That's what regional redundancy is supposed to look like.
We've run infrastructure in this region for 30 years. We've seen ice storms take out power across whole counties. If your DR plan assumes "different building" is the same as "different grid," you're going to find out the hard way that it isn't.
What About Latency to Spokane?
Forty-five minutes of driving distance translates to single-digit-millisecond network latency between Coeur d'Alene and Spokane — close enough that synchronous replication is realistic for most database workloads, far enough that a regional event doesn't take both sites down together. That's the balance DR architecture is supposed to hit, and a lot of "regional" DR sites get it wrong in one direction or the other — either too close (same grid, same fiber path, same flood plain) or too far (100ms+ round trips that make synchronous replication impossible).
How Does IDACORE North Compare to a Spokane Colo?
Here's the practical comparison for a company currently running production in Spokane and looking for a real DR site:
| Factor | Spokane Colocation | IDACORE North (Coeur d'Alene) |
|---|---|---|
| Distance from Spokane metro | 0 miles (same market) | ~35 miles / 45 min drive |
| Power grid | Shared regional utility risk | Separate Idaho Power grid |
| State jurisdiction | Washington | Idaho |
| Colocation pricing | Varies, often $350–450/kW/mo | $300/kW/month, no minimum |
| Contract minimum | Often 36 months | 12-month standard terms |
| Data residency | Washington state | Idaho — data doesn't cross state lines |
The pricing gap alone is worth noting. A company running a 10kW DR footprint pays $3,000/month at IDACORE North versus $3,500–4,500/month at comparable Spokane facilities — and that's before accounting for the actual redundancy benefit of a separate grid, which a same-market Spokane colo can't offer you at any price.
A Real Scenario: Regional Healthcare Provider
A healthcare network running EHR infrastructure in Spokane needed a DR site that satisfied their board's requirement for "geographic and infrastructure diversity" without adding latency that would break their replication window. They'd looked at Portland and Seattle — both added 20ms+ round trip time, too much for their synchronous database replication setup.
IDACORE North gave them sub-5ms latency to their Spokane primary, a different power grid, a different state's regulatory environment, and colocation pricing at $300/kW/month with no long-term contract lock-in. They deployed a half cabinet, 6kW, for $1,800/month. Total DR infrastructure cost, including transit, came in under $2,400/month — less than they were quoted for a Seattle facility with worse latency characteristics.
What Compliance Requirements Does This Satisfy?
If you're in healthcare, financial services, or any regulated industry, "same building, different floor" doesn't satisfy most auditors' definition of disaster recovery anymore, and increasingly neither does "same city, different provider." Regulators and auditors are asking harder questions about correlated failure risk — shared grid, shared fiber routes, shared regional weather exposure.
Idaho's data residency model also matters here separately from the DR conversation: data housed at IDACORE North stays in Idaho, full stop. It doesn't transit through Washington or get replicated to a facility that crosses a state line you didn't account for in your compliance documentation. For companies subject to state-specific data handling requirements, that boundary is a real answer to a question in an audit, not a footnote.
What Does IP Transit Look Like From Coeur d'Alene?
IDACORE North is on-net for the same committed-bandwidth IP transit we run everywhere else — our own ASN, our own BGP peering, not a resold circuit. Pricing is identical across all IDACORE locations: 100M commit at $170/month, 1G at $600/month, 10G at $2,000/month, up to 100G at $11,050/month, all billed 95th percentile. If your Spokane primary needs a private transport link to your Coeur d'Alene DR site, that's a conversation about your specific replication requirements — but the transit itself is priced the same whether you're buying it in Boise or North.
Frequently Asked Questions
Is Coeur d'Alene, Idaho a good disaster recovery site for Spokane, Washington businesses?
Yes. Coeur d'Alene is about 45 minutes from Spokane by car and sits on a separate power grid (Idaho Power vs. Avista/Washington utilities) and in a different state jurisdiction. That combination gives you real infrastructure diversity for DR without the latency penalty of a distant site — typically single-digit milliseconds round trip.
What does colocation cost at IDACORE North in Coeur d'Alene?
IDACORE North bills $300/kW/month on actual power draw, with no minimum power commitment and 1U minimum colocation available. A 6kW half-cabinet deployment runs $1,800/month. Standard contract terms are 12 months, shorter than the 36-month terms common among enterprise colocation providers.
Does IDACORE North keep data within Idaho?
Yes. IDACORE North, at 2115 N Government Way in Coeur d'Alene, is an Idaho facility, and data hosted there does not cross state lines. This matters for companies with state-specific data residency or compliance requirements who need documented, auditable data location.
Is IDACORE North currently accepting new colocation customers?
Yes. IDACORE North is open for active orders now, not in a pre-leasing or planning phase. Both per-U and full cabinet colocation are available immediately, with the same $300/kW/month pricing model used at IDACORE Boise.
How is IDACORE North different from IDACORE Boise?
Both facilities share identical pricing at $300/kW/month and the same 12-month standard contract terms. The difference is positioning: IDACORE North in Coeur d'Alene is purpose-built for Spokane-area disaster recovery and regional redundancy, while IDACORE Boise serves the Treasure Valley market directly with sub-5ms local latency.
If your DR plan currently depends on a Spokane facility sharing a grid with your primary site, that's a gap worth closing before you need it — talk to our team about a half-cabinet or full-cabinet deployment at IDACORE North and get a real quote on power, transit, and timeline at idacore.com/contact.
