How WISPS can reduced costs
Fixed-wireless ISPs operate on margins that reward efficiency. You've optimized tower placement, managed RF interference, and minimized truck rolls. But there's a line item on most WISP balance sheets that doesn't get the same scrutiny it deserves: IP transit.
Transit is easy to take for granted. You sign with a provider, set up BGP, and traffic flows. The problem is that transit bills scale with every subscriber you add and every gigabyte they consume. As your network grows — as it should — the cost grows with it, even for traffic that's going to the same handful of networks your customers use every day.
Peering at FD-IX changes that math. This post explains how and what it takes for a WISP to get connected.
Why WISPs Pay More Transit Than They Should
Most WISP customers use the internet the same way everyone else does: streaming video, browsing, social media, cloud applications, the occasional video call. The traffic sources behind all of that are concentrated. Cloudflare, Akamai, Netflix, Google, Amazon — a handful of major content networks account for the majority of downstream traffic on virtually every ISP in the country.
All of those networks have open peering policies. They will exchange traffic with you for free — if you're connected to an exchange where they're present.
If you're not peering, that same traffic travels through your transit provider. You pay per megabit for traffic that the content network would happily hand to you for free at an exchange. The margin on that traffic shrinks every time a customer streams in higher resolution, upgrades their plan, or adds a device.
What Peering Looks Like for a WISP
The mechanism is simpler than it sounds.
You connect your core router to FD-IX — either via a cross-connect if you have equipment in a colocation facility near the exchange, or via a Layer 2 transport circuit (remote peering) if you don't. You receive an IP address for the exchange LAN, configure a BGP session with the exchange's route server, and start receiving routes from member networks.
Traffic destined for Cloudflare, Akamai, or any other member network now exits your router directly to the exchange fabric instead of to your transit provider. You stop paying transit rates for that traffic. The exchange charges a flat port fee — at FD-IX, starting at $99/month for 100 Mbps or $275/month for 1G.
The content networks handle the rest. They're already connected. They want to exchange traffic with local ISPs. You just have to show up.
The Numbers: What a WISP Can Realistically Save
Every network is different, but here's a realistic scenario.
A WISP with 2,000 subscribers moves roughly 800 Mbps at 95th percentile during peak hours. Transit pricing at $3/Mbps costs about $2,400/month. A traffic flow analysis typically shows that 40–60% of that volume goes to a small number of major content networks — let's call it 350 Mbps.
If that 350 Mbps is shifted from transit to exchange peering:
- Eliminated transit cost: ~$1,050/month
- FD-IX port cost: $275/month (1G port)
- Net monthly savings: ~$775
- Annual impact: ~$9,300
For a WISP with tighter margins and higher traffic volumes, the impact is larger. For a WISP just starting to grow, even partial transit offload buys room to invest in infrastructure instead.
Do WISPs Actually Have What They Need?
The technical requirements for connecting to an exchange are minimal:
You need an ASN. This is an Autonomous System Number, issued by ARIN (the Regional Internet Registry for North America). If you're buying transit today with your own IP space, you almost certainly already have one. If not, ARIN can issue a single-homed ASN for a small fee.
You need your own IP address space. Provider-independent IP space, or IP space leased from a carrier, is required for peering. Again, most established WISPs already have this.
You need a BGP-capable router. Most WISPs running serious infrastructure — MikroTik, Juniper, Cisco, Arista — have BGP-capable equipment already. Configuring a peering session is not significantly different from configuring transit BGP.
You need access to an exchange location. This is the part that requires the most thought. If you have a point of presence in or near a city where FD-IX operates, a colocation cross-connect is straightforward. If not, remote peering via a transport circuit is the path.
Remote Peering for Rural WISPs
WISPs in rural markets often don't have a natural presence in a major metro data center. That's where remote peering comes in.
Remote peering extends your network to an exchange location via a dedicated Layer 2 circuit — MPLS or Ethernet — arranged through a carrier or transport provider. You don't need equipment at the exchange facility. Your circuit terminates at the exchange, you configure BGP the same way, and you get the same route server access and the same peering relationships.
The circuit adds cost — typically $500–$2,000/month depending on distance and provider. But for a WISP whose transit costs are high enough, the math still works. The break-even point depends on your traffic volume and current transit pricing.
FD-IX evaluates remote peering requests individually. If you're in a rural market in Indiana, Ohio, Illinois, Missouri, Kansas, Kentucky, Michigan, Texas, or surrounding states, reach out and we'll look at the options.
BEAD Networks: Build Peering In From the Start
If you're deploying a BEAD-funded network, you're designing infrastructure that will run for a decade or more. The transit cost model you start with is the cost model you'll live with — unless you plan ahead.
BEAD scoring rewards coverage and fiber miles. It doesn't reward network efficiency. But your operating costs will. A network designed with peering in mind — core infrastructure in or with access to an exchange location, routing policy built to shift content traffic off transit — will run more efficiently as subscriber counts climb.
Adding interconnection later is possible. It's also more expensive, more disruptive, and usually happens under pressure when transit costs have already become a problem. Planning for it now is cheaper and cleaner.
Getting Connected to FD-IX
The process:
- Verify you have an ASN and IP address space (contact ARIN if not)
- Review your current traffic flows to understand your transit usage profile
- Contact FD-IX at sales@fd-ix.com — we'll discuss your market and the best connection option
- If you're in or near an FD-IX market, we'll issue a Letter of Authority for a cross-connect
- If you need remote peering, we'll evaluate options and connect you with transport providers
- Configure BGP, connect to the route server, start exchanging traffic
Most connections go live in 7–14 business days. There are no setup fees. Port options start at $125/month.
Frequently Asked Questions
My network is small. Is an exchange worth it?
It depends on your transit costs and traffic mix. If you're paying transit rates on traffic that could be peering, the math often works even at relatively small scale. A $275/month port saving you $800+ in transit is worth doing.
I use a major transit provider. Can I still peer at an exchange?
Yes. Peering and transit are complementary. You continue buying transit for full internet coverage. You add peering to offload specific high-volume traffic. Most networks use both.
How do I know which of my traffic could be peered?
Your router or flow monitoring tool can show you the top ASNs your traffic is destined for. Cross-reference those with FD-IX member networks. The overlap is usually significant.
What if my BGP configuration is wrong?
FD-IX provides BGP configuration support for new members. You don't need to figure it out on your own. We'd rather you connect successfully than not connect at all.
The Bigger Picture
WISPs built the fixed-wireless industry on operational efficiency. The ability to deliver broadband where fiber couldn't go, at a cost structure that made business sense, required being lean at every layer of the stack.
Transit is not a lean cost. It's a variable expense that scales against you. Peering converts part of that variable cost into a flat monthly fee — and keeps more of the economics of your network on your side.
FD-IX exists specifically to make that conversion accessible to networks in the Midwest. If you're a WISP operating in this region, we'd like to talk.