IDACORE Boise sells IP transit on committed bandwidth tiers billed at the 95th percentile: 100M at $150/month, 1G at $450/month, 10G at $1,350/month, and 100G at under $10,000/month. That's flat per-Mbps pricing from our own ASN, on-net across all three IDACORE facilities, with no egress surprises.
What Does Committed Bandwidth Actually Cost at IDACORE Boise?
Let's start with the numbers, because that's what you came for.
| Commit Tier | Monthly Price | Effective $/Mbps |
|---|---|---|
| 100M | $150 | $1.50 |
| 1G | $450 | $0.45 |
| 10G | $1,350 | $0.135 |
| 100G | $9,750 | <$0.10 |
This is 95th percentile billing on a committed tier. You pick your commit, we bill your actual usage against it, and the top 5% of traffic spikes get thrown out before billing — standard ISP practice, not a gimmick. If you burst above your tier occasionally, you're not getting a shock invoice. If you're consistently blowing past it, that's a signal to upgrade your commit, and we'll tell you that directly instead of letting an overage line item pad our margin.
Compare that to hyperscaler egress. AWS charges $0.09/GB after the first 10TB free, dropping to around $0.05/GB at high volume — but that's billed per gigabyte transferred, not per Mbps committed. A company pushing 10Gbps sustained (roughly 3.2 petabytes a month) would pay somewhere north of $150,000/month in AWS egress at standard rates, even with volume discounts applied. Our 10G commit at IDACORE Boise is $1,350/month, flat, regardless of whether you push 1TB or 3PB across that pipe. That's not a rounding difference. That's the entire economic argument for colocation with real transit versus hyperscaler dependency.
Why Does IDACORE Run Its Own ASN Instead of Reselling Transit?
Because we've done this before — outside of IDACORE. Before this company existed, part of our team founded and ran an ISP with our own ASN, peering at the Seattle Internet Exchange. We know what a BGP session actually looks like when it flaps at 2am. We know the difference between a provider who can pull up a real-time route table and one who opens a ticket with an upstream and waits.
That matters here because IP transit is a service we operate, not a service we buy and mark up. When you're on our network, your routes are announced from our ASN, and our engineers make the peering and traffic engineering decisions — not a reseller's NOC three time zones away reading from a script.
IDACORE Boise carries 7 on-net carriers: Zayo, Lumen/Level 3, Cogent, CenturyLink, Syringa, Cable One, and Hurricane Electric. That diversity means we can route around a bad path instead of being stuck on whatever single upstream a reseller happened to contract with. If Cogent has a bad day into a particular region, we shift. You don't notice. That's traffic engineering, and it's only possible because we hold the routing decisions ourselves.
What Does On-Net Actually Mean for Your Latency?
On-net means the carrier has infrastructure physically present in the building — no local loop, no third-party middle-mile handoff eating milliseconds. From Boise, that translates to real numbers: 23ms to Seattle, 22ms to Portland, 14ms to Salt Lake City. For a Treasure Valley business, we're seeing sub-5ms to local endpoints, which matters if you're running anything latency-sensitive for regional customers — POS systems, VOIP, real-time applications.
How Does This Compare for a Real Deployment?
Take a mid-size e-commerce company running a cluster of application servers plus a CDN origin in Boise. Say they're pushing a sustained 2Gbps average with bursts to 4Gbps during sales events — call it 700TB a month.
On AWS, at roughly $0.05-0.09/GB blended after free tier, that's somewhere between $35,000 and $60,000/month in egress alone, before compute. On IDACORE Boise, they'd size to our 1G commit if their sustained average lands closer to 1Gbps with headroom, or step up to a 10G commit at $1,350/month if they need real burst capacity for those sales events. Either way they're paying a fixed number every month regardless of how good (or bad) that sales event goes. That's the part hyperscaler billing can't give you — the moment your product succeeds and traffic spikes, egress punishes you for it. Committed transit doesn't.
Add colocation into the same scenario. IDACORE Boise bills colocation at $300/kW/month based on power draw, not rack space — a rack pulling 3kW costs $900/month regardless of whether it's a 1U server or a half-populated 42U cabinet. Combine that with a 10G transit commit at $1,350/month and you've got predictable infrastructure costs you can put in a budget spreadsheet and not touch for a year.
What Contract Terms Come With Boise Transit?
Standard terms at IDACORE Boise run 12 months. Most enterprise transit and colocation providers lock you into 36-month terms as standard — we don't. If our service is worth keeping, you'll renew. If it's not, you shouldn't be stuck for three years finding that out.
We're also SOC 2 Type II, PCI DSS, NIST 800-53, SSAE-16, and HITRUST CSF certified, so if your transit and colocation need to sit inside a compliance boundary — healthcare, financial services, government contracts — that groundwork is already done. And your traffic stays in Idaho. Data residency isn't a policy statement here; it's physical: your packets don't have to cross state lines to get from your rack to your BGP peer.
Frequently Asked Questions
What is 95th percentile billing and how does it work for IP transit?
95th percentile billing measures your bandwidth usage in 5-minute intervals over a month, discards the top 5% of samples (your traffic spikes), and bills you based on the highest remaining value. It protects you from being billed for brief bursts while still reflecting your real sustained usage. IDACORE bills all transit tiers this way, from 100M through 100G commits.
How much does 10Gbps of IP transit cost in Boise, Idaho?
A 10G committed bandwidth tier at IDACORE Boise costs $1,350/month, or roughly $0.135/Mbps, billed at 95th percentile. That's flat and predictable regardless of actual data volume moved, unlike hyperscaler egress billing which scales per gigabyte and can run tens of thousands of dollars for equivalent sustained throughput.
Which carriers does IDACORE Boise connect to on-net?
IDACORE Boise has 7 on-net carriers: Zayo, Lumen/Level 3, Cogent, CenturyLink, Syringa, Cable One, and Hurricane Electric. On-net means physical presence in the building, so there's no local loop or third-party handoff between your rack and the carrier's network.
Does IDACORE resell transit from another provider?
No. IDACORE operates its own ASN and manages its own BGP peering and traffic engineering. This traces back to our team's history founding and running an ISP with peering at the Seattle Internet Exchange. Routing decisions are made in-house, not outsourced to an upstream reseller's support queue.
How does Boise transit pricing compare to AWS data transfer costs?
AWS egress runs roughly $0.05-0.09/GB depending on volume, billed per gigabyte moved — costs that scale directly with your traffic and business growth. IDACORE Boise transit is a flat monthly commit: a 10G tier is $1,350/month regardless of whether you push 1TB or 3 petabytes. For sustained high-bandwidth workloads, the gap can run into tens of thousands of dollars a month.
Ready to see what your actual traffic pattern would cost on a committed tier instead of per-gigabyte egress? Talk to our network engineers about sizing an IP transit commit for your Boise deployment.
