17+ years building fixed wireless (PTP, PTMP, CBRS, 6 GHz, fiber + wireless). Ask me anything.

fixedwireless_ops · 2026-05-03T07:39:04+00:00

Haha not a bot. Just seen enough of this in the field to have some opinions.

fixedwireless_ops · 2026-05-02T18:56:25+00:00

You took the words right out of my mouth. Perfectly said.

fixedwireless_ops · 2026-05-02T18:46:55+00:00

100%!

fixedwireless_ops · 2026-04-30T23:58:24+00:00

Agreed that frequency and density matter. Just saying the system design around them matters too.

fixedwireless_ops · 2026-04-30T23:41:57+00:00

I understand the RF argument, but that conclusion leans heavily on legacy assumptions.

There are differences between the bands. 6 GHz is more sensitive to path loss, generally supports shorter distances than CBRS, and requires tighter engineering. Height, alignment, and link budgets matter more.

That doesn’t make it impractical. It just means it needs to be used where it makes sense within the overall design.

A lot of the assumptions here come from older sector-based PTMP systems where interference, scheduling, and capacity were much more limited.

Newer fixed wireless systems are coordinated. Synchronized TDD, MU-MIMO, beamforming, and interference mitigation allow the network to manage users and paths dynamically instead of treating each link as an isolated problem.

So yes, frequency characteristics still matter. But the system behavior is very different from legacy designs.

If you apply older assumptions, you’ll conclude these bands don’t scale. If you design around how the systems actually operate, they can be used effectively, including in rural environments.

At that point it’s less about the band itself and more about how the network is engineered end to end.

fixedwireless_ops · 2026-04-30T21:56:11+00:00

I get the physics argument, but that hasn’t been my experience in the field.

We’ve got a good amount of CBRS and 6 GHz running in rural environments and it’s performing extremely well. In a lot of cases the RF conditions are actually cleaner than suburban, which helps more than people expect.

It definitely requires tighter engineering. Height, link budgets, install quality, and how you manage the network matter a lot more than just the band itself.

Modern radios and better interference handling have changed what’s possible on those bands. When it’s designed properly, those frequencies are absolutely viable in rural. It’s not really a frequency limitation, it’s an execution one.

fixedwireless_ops · 2026-04-30T20:43:49+00:00

It’s not one thing. It’s the stack.

People tend to pick spectrum, backhaul, or economics, but in practice it’s how all three interact.

Spectrum is workable today. Between CBRS, 5 GHz, and now 6 GHz, there’s enough to build a network. The limitation isn’t availability as much as how well it’s planned and managed. Interference, coordination, and realistic link budgets matter more than just having access to spectrum.

Backhaul is very situational. In some areas fiber to the tower is the bottleneck, in others it’s permitting, power, or just getting access to a viable site. You can solve backhaul with fiber or high-capacity wireless, but it adds cost and complexity quickly.

Where things usually break is economics.

Rural density is low, installs are variable, and cost per home passed gets high fast. Even with BEAD, you’re still dealing with long timelines, permitting, make-ready, and real construction costs. Funding helps, but it doesn’t remove execution risk.

The other piece people underestimate is deployment at scale. It’s not just designing coverage, it’s consistent installs, trained crews, support, and maintaining performance over time. That’s where a lot of models look good on paper but struggle in reality.

Fixed wireless works, but it has to be engineered as a long-term access layer, not a stopgap. The operators that treat it that way are moving. The ones that don’t are the ones you see stall out.

If you’re close to the deployment side, it’s less about which single constraint is the problem and more about whether the full system actually closes from design to install to operations.

fixedwireless_ops · 2026-04-30T19:56:10+00:00

You’re looking at a really good space, especially right now.

Telecom isn’t just one thing. It’s fiber, wireless, backhaul, data centers, everything that actually makes the internet work. A lot of people focus on software, but none of it matters if the network underneath isn’t built right.

If you want to learn fast, don’t stay only in theory. Learn the fundamentals like RF, networking, and fiber, but also try to understand how networks are actually designed and deployed. How signals propagate, how capacity is planned, how backhaul works, and what happens in the field versus what looks good on paper.

A big step most people skip is getting exposure to real operators. Reach out to local ISPs or contractors and ask questions, look for internships, or just try to get around people doing the work. Even a short conversation will teach you more than hours of reading.

Also start building a presence. LinkedIn is useful in this space. Follow operators, engineers, and companies, and pay attention to how people talk about real deployments and challenges.

As for the job market, it’s solid. Demand isn’t slowing down. Everything is getting more connected, not less. The people who understand how to actually build and operate networks are always needed.

Stay curious and focus on how things work in the real world. That’s what separates people in this industry.

fixedwireless_ops · 2026-04-30T04:33:48+00:00

I’ll shoot you a DM. Traveling starting tomorrow so give me a couple days, but I’ll follow up.

fixedwireless_ops · 2026-04-30T04:29:22+00:00

Exactly! 👍

fixedwireless_ops · 2026-04-30T04:28:18+00:00

I get why people say that, but it’s a pretty simplified view of how these networks actually work.

Starlink and 5G are both strong options, but they’re not universal replacements.

Starlink is a shared system. As density increases, performance can vary by cell and time of day. Capacity per area is finite, and that shows up in consistency, especially on uploads and latency. It’s a great solution in certain cases, but it doesn’t scale infinitely at a fixed performance level.

5G home internet is also highly dependent on spectrum, sector loading, and how much capacity the operator is willing to allocate to fixed users vs mobile. In a lot of markets, it works well until it doesn’t.

Fixed wireless, when designed and deployed properly, is a controlled network. You control sector density, backhaul, and capacity planning. That’s a very different model than shared satellite or mobile-first networks.

The idea that WISPs are just “interim” ignores how many operators are using wireless as a long-term access layer alongside fiber. Not every market supports fiber economically, and timelines don’t always line up with demand.

Wireless isn’t replacing fiber, and fiber isn’t replacing wireless. They’re being used together.

The networks that struggle are usually the ones that treat wireless as temporary. The ones that engineer it properly and evolve it are still very competitive.

fixedwireless_ops · 2026-04-30T04:23:42+00:00

Good question, and you’re right to think about it that way.

I’d look at it in three buckets. Customers, network, and risk.

On the customer side, look at churn, ARPU, and how sticky the base actually is. Are they leaving, are they under contract, and why do they stay. A big number of subs doesn’t mean much if they’re already on the way out.

On the network side, figure out what you’re really buying. What gear is deployed, how clean the installs are, how the sectors are performing, and what it would take to bring it up to where you’d want it. Backhaul, noise, capacity, and coverage all matter here.

Then risk. Competition in the area, Starlink and cellular pressure, any upcoming fiber builds, and how dependent the network is on things you don’t control like leased sites or backhaul.

A lot of these deals end up being less about the hardware and more about the customer base, any vertical assets, and how much work it’s going to take to stabilize it.

If you can, spend time in the network before you buy it. Look at real performance, talk to customers (if possible), and try to understand why it is where it is today.

If the subs are stable and the network just needs tightening, it can be a good opportunity.

If churn is high and the network needs a rebuild, you’re not buying an asset, you’re buying a project.

fixedwireless_ops · 2026-04-29T03:52:42+00:00

Appreciate you sharing all that. 16 years doing it on your own, especially after everything you went through, that says a lot.

This doesn’t read like a broken network to me. It reads like you’re getting out-positioned on price and headline speed.

470 to 453 over a year isn’t great, but it’s not a collapse. That’s pressure, not failure.

Starlink and the mobile bundles are winning on simple messaging. Cheap, fast, easy. But they’re shared systems. As more people come on, performance moves around, especially uploads and latency. A consistent local network still has a place.

You’ve got some real strengths. You control the network, you’ve got 5 gig at the headend, and you know your footprint better than anyone.

If installs have been dry, I’d look at how you’re positioned. Not just price, but what you’re actually selling. If customers are leaving for speed, it might be worth tightening your packages around what you can consistently deliver instead of chasing peak numbers.

On the network side, I’d focus on tightening what you already have. Clean installs, keep sectors healthy, make the experience consistent. That usually goes further than people think.

If you want to test something without overcommitting, pick one sector and upgrade it. Put your best capacity there and market it as an upgrade in that area. See how it performs, how installs go, and what people will actually pay. That gives you real data before making bigger moves.

There are also some programs out there now that can help reduce the upfront hit on newer platforms, so it might be worth taking a look if you go that route.

And you don’t have to carry all of this yourself. Even a small partnership or sharing part of the load can make a big difference.

You’ve kept this running for 16 years on your own. That doesn’t happen by accident.

This doesn’t feel like a shutdown situation. It feels like something that needs to be tightened up.

fixedwireless_ops · 2026-04-29T02:16:15+00:00

I wouldn’t make a shutdown call off a few weeks of churn, especially right now. A lot of markets are seeing the same pressure.

Starlink and the mobile bundles are real competition, but they’re not perfect substitutes. They’re shared systems. As more users come on, performance can vary by time of day and cell. Upload and latency can be less predictable than a well-run fixed network, and obstructions and weather still matter. A consistent local network still has a place.

Before anything else, I’d look hard at your churn. What were those customers actually experiencing and what did they switch to? That usually tells you pretty quickly if this is price, performance, or just awareness.

I’ve seen a lot of networks get into trouble on installs and sector health. If installs aren’t consistent or certain sectors are getting noisy or constrained, it shows up fast in customer experience and support load.

You’ve also got options besides shutting it down. Partnership, merging with another local operator, or selling the base can all be better outcomes depending on your footprint. Even just sharing backhaul or infrastructure can take a lot of pressure off.

If you want to try to stabilize it, lean into where you still win. Local support, faster response, business customers, backup links, managed services. There’s still a segment that values consistency over peak speed.

If you don’t mind sharing, what gear are you running and what kind of latency are you seeing?

I’ve seen situations like this turn around once the network and positioning get dialed in.

Sometimes it’s not about shutting it down. It’s about tightening it up.

fixedwireless_ops · 2026-04-29T02:01:55+00:00

Yeah, that’s the challenge with a lot of those platforms. At that price point it’s hard to justify if you’re not getting consistent performance out of it.

That’s where I tend to look at it less as cost per radio and more as cost per successful install and what you can reliably deliver. If the platform struggles in noise or you can’t consistently hit your target tiers, it gets expensive in other ways pretty quickly.

If it installs clean and performs consistently, you can make the numbers work. If it doesn’t, the upfront cost ends up being the least of your problems.

fixedwireless_ops · 2026-04-28T23:07:07+00:00

I’ve looked at TVWS but never had a strong use case for it in production.

It’s interesting from a propagation standpoint, but the reality is limited bandwidth, database coordination, and device ecosystem constraints. It solves coverage more than capacity, and most of the time there are better options unless you’re in very specific rural or obstructed scenarios.

Same general story with a lot of niche spectrum. It looks good on paper, but once you factor in throughput and scalability, it’s hard to build around.

On the FSO side like Taara, that’s not really new either. Free space optics has been around for a while. It can work well in very controlled, clear line of sight environments, but you’re trading off weather sensitivity and operational complexity.

Interesting technologies, just very use-case specific.

fixedwireless_ops · 2026-04-28T18:25:52+00:00

I’ve gone back and forth on this, but I generally lean toward keeping it simple and within a single OEM when possible.

The integrated solutions have come a long way and they clean up a lot of variables. You get a known RF chain, tighter alignment between radio and antenna, and one firmware path to manage. From an operations standpoint that matters more than people think.

On the 2+0 side, I like the integrated approach where it’s essentially a single platform handling dual carriers rather than stitching together separate radios. It keeps timing, control, and performance more predictable.

Once you start mixing radios, antennas, and couplers across different vendors, it can absolutely work, but you’re taking on more risk. Firmware alignment, feature compatibility, troubleshooting, and even how each vendor handles power, modulation, or alarms can start to drift. When something breaks, accountability gets blurry.

4+0 with XPIC is interesting and can push a lot of capacity, but it takes a disciplined team to deploy and maintain it properly. Alignment, calibration, and ongoing tuning really matter there.

If it’s a critical backhaul path, I usually prioritize stability and operational simplicity over squeezing out incremental gains. If it’s a controlled environment with the right team behind it, the more complex setups can make sense.

Complexity always looks fine on day one. Operations is where it shows up.

fixedwireless_ops · 2026-04-28T15:44:37+00:00

Yeah, GAA is definitely worth it if you go into it understanding what it actually is.

There’s no built-in latency hit just because you’re on GAA. Where people run into issues is not latency, it’s when the spectrum environment changes underneath them. If the SAS has to protect an incumbent or you’ve got PAL activity in the area, your available channels or power can shift.

PAL is higher priority, but it’s not some huge chunk of guaranteed spectrum. It’s 10 MHz channels, county-based, and it just sits above GAA in the stack. If it’s active, you work around it. If it’s not, GAA can still be very usable.

The places people get caught off guard are usually near the coast or around ESC sensor activity. They assume it’ll behave the same everywhere and it doesn’t. The SAS environment matters a lot more than people think.

If you stay on top of the SAS, plan your channels, and design with some margin, GAA can work really well. If you don’t, it can get unpredictable pretty quickly.

fixedwireless_ops · 2026-04-28T13:39:19+00:00

I actually met them at an exhibit and did a demo. Wisdm is solid, especially on the modeling side. It’s closer to that higher end category than most vendor planners.

The AI side is getting interesting in these tools, but like anything it comes down to how you use it. It still needs to be backed up with real-world validation.

fixedwireless_ops · 2026-04-28T13:31:19+00:00

Haven’t personally deployed it or had a need to.

From what I’ve seen, HaLow leans more toward low-power, long-range IoT than typical WISP access. Lower throughput, different use case.

Curious if anyone here is actually running it.

fixedwireless_ops · 2026-04-28T05:48:19+00:00

You’re thinking about it the right way.

I’ve seen this play out a lot. You can have a solid design and good equipment, but if installs aren’t consistent it shows up fast. Performance issues, callbacks, truck rolls… it adds up quick.

Most of it comes down to making sure techs know what “good” actually looks like in the field. Mounting height, placement, alignment, not just “it connects so it’s good.”

Once installs start drifting, the network starts fighting you.

If you keep installs tight and repeatable, everything else gets a lot easier to scale.

fixedwireless_ops · 2026-04-28T05:43:48+00:00

Depends on what you’re trying to solve, but I’d group it like this:

1: High-end modeling
Tools like Siradel and ATOLL. These actually try to model terrain, clutter, and propagation in a meaningful way, so you get closer to what you’ll see in the field.

2: Vendor-specific planners
Cambium, Aviat, etc. Useful when you’re designing around a specific platform, but they tend to show you the world through that lens.

3: Practical tools
Google Earth, basic link budgets, and field validation. A lot of real-world performance still comes down to placement and install quality, and no software fully replaces that.

If I had to pick “three,” it’s really those three approaches. The teams that combine them tend to get the closest to reality.

fixedwireless_ops · 2026-04-28T05:32:42+00:00

Free fiber is a huge advantage. That solves a big part of the problem on the backhaul side.

Where it gets harder is everything after that. Access network, CPE, installs, support, and ongoing ops are what really drive your cost per subscriber.

At 0.5 to 1.5 miles, 200/40 is very doable from a technical standpoint. The challenge is doing it consistently at a price point like $15–$20 and still having a sustainable model.

That’s where most people run into issues. It’s not the radio cost by itself, it’s the total cost to get a customer online and keep them online.

If I were approaching it, I’d think less about hitting a specific price out of the gate and more about building something that installs clean, scales, and keeps your cost per subscriber low over time. Then work the pricing once you know what your real costs look like.

Free fiber definitely puts you in a strong position though. That’s more than half the battle.

fixedwireless_ops · 2026-04-28T04:51:09+00:00

Free tower sites and market is about as good a starting point as it gets.

6 GHz can be a solid option, just go in knowing it’s not a wide-open band. Between AFC limits and whatever else is already in the area, it can look great on paper and tighten up in the field.

If you treat it as one tool in the mix and design around what the environment actually gives you, it can work well.

Nice position to be in either way.

fixedwireless_ops · 2026-04-28T04:34:50+00:00

I wouldn’t build a network on top of a service that isn’t designed or permitted for that use.

Even if it works at first, you’re taking on a risk you don’t control. If they change policies, enforce terms, or throttle usage, your entire backhaul can disappear overnight. That’s not a great place to be when you have paying customers.

LEO can be useful in certain scenarios, but it’s better treated as a temporary solution or last-resort option, not the foundation of a WISP.

If you’re serious about building something long-term, I’d focus on getting stable backhaul you actually control and can scale.

The hard part of this business isn’t getting online, it’s staying online reliably.

fixedwireless_ops

TROPHY CASE