The fastest path to everyone in Idaho.
Delivered in-state — not hauled to Seattle and back.
Verify us before you talk to us — our PeeringDB record.
Most Idaho bandwidth isn’t delivered in Idaho.
It’s hauled to Seattle or Salt Lake, handed off there, and hauled back. Two Idaho networks a few miles apart can end up passing traffic through a facility 500 miles away — and paying for the round trip in latency they never see itemized on an invoice. That’s 20 milliseconds spent before a single packet does anything useful.
We built IDACORE to not do that.
We buy transit only from carriers with real routers in-state and a real local handoff. If a provider’s “presence” here is a circuit that terminates somewhere else, we don’t buy it — no matter what it costs. That single rule is why traffic on our network reaches Idaho destinations in single-digit milliseconds instead of taking a detour through another time zone.
Local means local.
Ordering a circuit from a national carrier is a process with its own vocabulary. Quote requests routed to a sales team three states away, an order that sits in provisioning while somebody validates serviceability, an install date that moves twice, and a support number that connects you to a queue in another country where the first person you speak to has never heard of your city.
We’re here. Quotes come back in days, not weeks, and we turn up service within five business days of a signed order at any facility we serve. When something breaks, the number on your invoice reaches an engineer in Idaho who already knows your circuit. The same decision that keeps our traffic off the Seattle hairpin is the one that puts that engineer on your call.
Everything on this list is standard.
A real BGP session.
We operate AS36824 with our own directly-allocated IPv4 and IPv6 space and our own routing policy. Bring your prefixes and your ASN and we’ll carry them; if you don’t have space, we’ll assign it and route it. You get a session with the controls a real network needs — not a static route.
Native dual-stack.
Full IPv4 and IPv6 tables, default-only, or both. Your choice at turn-up. IPv6 is provisioned on day one, not a tunnel and not a line item.
Carrier-diverse upstream.
Multiple tier-1 upstreams on physically separate paths under separate ASNs. Not two circuits from the same underlying carrier dressed up as diversity — a distinction worth verifying on every quote you get, including ours.
Traffic engineering that works.
Standard BGP communities to set local preference, prepend, or suppress announcement toward a specific upstream. A remote-triggered blackhole community drops an attack at our edge before it ever reaches your port.
Routing security by default, not as an upsell.
Published RPKI ROAs and registered IRR objects, so your prefixes propagate into upstream filters without a support ticket every time you add one. Bogon and RFC1918 filtering, per-neighbor prefix limits, TTL security, and prefix filters in both directions on every session. You inherit the whole posture.
Sub-second failure detection.
BFD on transit and customer sessions. Convergence measured in hundreds of milliseconds, not the ninety-plus seconds a default BGP hold timer costs you.
Service-provider hardware.
Purpose-built carrier routers with hardware forwarding, full dual-stack table capacity with years of headroom, and 1G, 10G, and 100G ports. Not a repurposed enterprise switch running an internet table it was never scoped for.
Per-customer flow visibility.
Full flow telemetry across the edge. When you ask where your traffic is going, you get an answer with numbers in it.
A 100% uptime SLA.
Any downtime at all earns a credit — not a 99.9% target that quietly forgives the first forty-three minutes of every month.
Published rates. No quote required to compare.
Billed on committed bandwidth and measured at the 95th percentile, with overage billed per Mbps above your commit. The same rates apply at all three IDACORE locations.
| Commit | Monthly | Per Mbps |
|---|---|---|
| 100 Mbps | $150 | $1.50 |
| 1 Gbps | $450 | $0.45 |
| 10 Gbps | $1,350 | $0.135 |
| 100 Gbps | $9,750 | $0.098 |
Networks that measure their own latency.
Hosting and VPS providers, WISPs, regional ISPs, and enterprises running their own ASN. Municipalities, healthcare systems, and non-profits that need dependable, low-latency connectivity without the overhead of running their own routing — we’ll handle the BGP side or hand off a clean routed block, whichever fits your team.
And anyone who needs transit in Idaho and would rather buy it from the network that already terminates here.
Common questions about IDACORE IP transit.
What is IDACORE’s ASN?
IDACORE operates AS36824 with directly-allocated IPv4 and IPv6 address space and its own routing policy. Our network record is published at peeringdb.com/net/1199.
How much does IP transit cost at IDACORE?
IP transit is priced on committed bandwidth from 100 Mbps to 100 Gbps, with the per-Mbps rate dropping as commit rises: 100M is $150/month ($1.50/Mbps), 1G is $450/month ($0.45/Mbps), 10G is $1,350/month ($0.135/Mbps), and 100G is $9,750/month (under $0.10/Mbps). Usage is measured at the 95th percentile, with overage billed per Mbps above your commit.
How long does it take to turn up an IP transit circuit?
Five business days from signed order at any facility we serve. Quotes come back in days rather than weeks, because there is no handoff to a sales or provisioning team in another state.
Can I bring my own IP space and ASN?
Yes. Bring your prefixes and your ASN and we will carry them over a standard BGP session. If you do not have your own address space, we will assign and route space for you instead.
Does IDACORE support IPv6?
Yes. Every session is natively dual-stack, and IPv6 is provisioned on day one at no additional charge — not tunneled and not billed as a separate line item. You can take full IPv4 and IPv6 tables, default-only, or both.
What port speeds are available for IP transit?
Handoffs are available at 1G, 10G, and 100G on purpose-built carrier routers with hardware forwarding and full dual-stack table capacity.
Does IDACORE support BGP communities for traffic engineering?
Yes. Standard BGP communities are available to set local preference, prepend, or suppress announcement toward a specific upstream. A remote-triggered blackhole community lets you drop an attack at our edge before it reaches your port.
Does IDACORE publish RPKI ROAs?
Yes. IDACORE publishes RPKI ROAs and registers IRR objects, so customer prefixes propagate into upstream filters without a support ticket for every addition. Sessions also carry bogon and RFC1918 filtering, per-neighbor prefix limits, TTL security, and prefix filters in both directions.
What is the IP transit SLA?
IDACORE offers a 100% uptime SLA on IP transit — any downtime at all earns a service credit, rather than a tiered target that excuses the first several minutes of outage each month.
Where is IDACORE IP transit available?
IP transit is available on-net at all three IDACORE locations — Boise, East in Eastern Oregon, and North in Coeur d’Alene — with private transport available between sites for multi-site deployments.