Your coverage map shows who is served. It doesn't show who is served by exactly one tower. GridVisio's Redundancy view colours the same subscriber markers by how many separate towers could actually serve each customer — so single points of failure stand out before an outage finds them for you.
The same subscribers, coloured by how many towers can reach them
Coverage asks "is this customer served?" Resilience asks "what happens when the tower serving them stops?" Most planning tools only answer the first.
On a normal coverage map, a subscriber reachable by four towers and a subscriber clinging to one marginal link are the same shade of green. They are not the same business risk.
Flip the Redundancy view toggle, right under the Subscribers layer, and the map re-colours in place — same markers, same positions, different question:
Filter to just the amber ones and you have a concrete work list: the customers whose service depends entirely on one site staying up.
Hover any subscriber to see exactly which towers could serve it
Being in range is not the same as being a real option. A fallback that can't carry the customer isn't a fallback.
Every candidate tower is tested with the same terrain- and LiDAR-aware propagation engine as the rest of GridVisio, then measured against your own project's signal thresholds. An option that's geometrically in range but too weak to sell is listed — and explicitly does not count.
Two sectors on the same tower are still one tower. If that site loses power, both go with it. GridVisio counts distinct towers, so a subscriber covered twice from one mast is correctly flagged as a single point of failure — not quietly marked redundant.
Hover a subscriber for a compact table of every tower and sector that reaches it, best first, with the predicted signal for each and a tick or cross for whether it genuinely qualifies. No guessing which tower the fallback would actually be.
Redundancy updates whenever coverage is reclassified — adding, moving, editing or removing a tower or sector, or changing a subscriber. There's no separate report to remember to re-run.
This isn't a new analysis bolted on top. When GridVisio classifies coverage, it already tests every tower and sector that could reach each subscriber, at full precision — then keeps the best one and discards the rest.
The Redundancy view simply keeps what was already being calculated. Turning it on costs no additional terrain lookups, no additional propagation runs, and no additional time on your coverage recalculations.
Existing projects need one coverage recalculation to fill in the history — GridVisio offers it the first time you open the view, and never starts it without you asking.
Resilience across an entire subscriber base at a glance
Redundancy data turns a vague worry into a sorted list.
| Situation | What the Redundancy view tells you |
|---|---|
| Planned maintenance on a tower | Exactly which customers have no alternative and will genuinely go dark — so you can notify the right people instead of all of them. |
| Deciding where the next tower goes | A cluster of amber subscribers is a resilience case for a site, separate from the coverage case white area detection already makes. |
| Retiring or relocating a site | Who loses service entirely versus who simply fails over, before the decision is made rather than after. |
| Selling an SLA or business tier | Which addresses can honestly be offered a resilient service today, and which would need another tower first. |
| Grant and funding documentation | Evidence about network robustness, not just coverage extent. |
Import your subscribers, add your towers, and see which customers depend on exactly one site. 14-day trial, no credit card.
Start free trial