Use case · 5G WAN

Keep taking payments when the main internet line fails.

A cut cable or carrier outage shouldn't close a store or clinic. 5G failover takes over automatically for the traffic that matters, then hands back when the main line recovers.

TYPICAL SITEStores, restaurants, clinics
WHAT HURTSOutages close the doors
WHAT WE CHANGEAutomatic 5G backup
Sound familiar?

What it looks like day to day.

A typical scenario based on the environments we work in, not a specific customer.

  • An outage means closed registers or turned-away patients
  • There's a backup, but someone has to switch it manually
  • The line looks 'up' but apps aren't working
  • You find out about outages from customers
Line cut, site offline compared with 5G takes over automaticallyNetwork topology. Existing: Line cut, site offline. Proposed: a 5G gateway connects the site router through the carrier network to the internet and applications.AEXISTING CONDITIONSNTSSITEINTERNET / APPSFIBER / ISPDOWNEDGE RTRPOS · VOICEOFFLINEEXISTING── WIRED ╌╌ WIRELESSBPROPOSED DESIGNNTSSITEINTERNET / APPSFIBER / ISPDOWNEDGE RTRPOS · VOICE5G GWCARRIER RANACTIVEONLINEPROPOSED · 5G WAN · MONITORED── WIRED ╌╌ WIRELESSA — Line cut, site offlineB — 5G takes over automatically
Sheet A shows existing conditions; sheet B shows the proposed design. Illustrative, not to scale.
Why it happens

A backup only helps if it takes over on its own.

Good failover watches whether your apps actually work, not just whether the cable is plugged in. It moves the important traffic first and comes back without flapping between links.

What we do

How we fix it.

5G WAN connects a location to the internet over the cellular network, as its main connection, its backup, or a separate path for emergency access.

  1. Check coverage at each site

    A coverage check picks the best carrier and antenna.

  2. Set the priorities

    Payments, voice and key apps go first on backup.

  3. Automate the switch

    Health checks trigger failover and a clean return.

  4. Watch the links

    Alerts when a site fails over, with 24/7 monitoring on our managed option.

Every site starts with a coverage check for each carrier, so the right carrier and antenna are picked before anything ships.

What changes

What's different after.

Stay open

Payments and key apps keep running.

No manual steps

Failover happens on its own.

Know first

You hear about outages before customers do.

Is it a fit?

Where this works, and where something else fits better.

We recommend what solves the problem, even when it's a different solution.

A good fit for

  • Stores, restaurants and franchises
  • Clinics and pharmacies
  • Branches and offices that can't go dark

Something else may fit better

  • Sites that need full-speed backup for heavy video or large transfers may need a second wired line
For your IT or engineering team

Technical detail

The design decisions, the end-to-end path and how the result is tested.

Show

Failover should respond to a path that cannot reach required services—not only to a cable that is physically disconnected.

Design decisions

Design decisionWhat we need to understandHow we engineer it
Health probesSelect multiple targets and measurements for DNS, internet, data center, and critical applications.Declare failure only from meaningful, policy-controlled evidence.
Traffic priorityClassify payment, voice, operations, cameras, guest, updates, and bulk traffic.Fit essential applications inside measured cellular capacity.
FailbackDefine stability timers, session impact, preferred-path return, and change logging.Recover deliberately without repeated path oscillation.

The end-to-end path

  1. PRIMARY PATHFiber · broadbandNormal preferred transport
  2. ALTERNATE PATHLTE / 5G gatewayIndependent measured access
  3. WAN POLICYHealth · route · prioritySelect, protect, and recover
  4. BRANCH WORKPayment · voice · cloudThe service that must continue

Path diversity should include power, cabling, provider, last-mile route, upstream network, and destination dependencies—not just two ports on one appliance.

How the result is tested

  • Hard-failure test Disconnect the primary access and measure detection and recovery.
  • Soft-failure test Simulate loss, DNS failure, upstream routing failure, and destination unreachability.
  • Capacity test Run prioritized applications within measured cellular capacity.
  • Session test Observe payment, voice, VPN, and cloud sessions during path changes.
  • Failback test Create intermittent recovery and confirm anti-flap behavior.
  • Operations test Verify alerting, escalation, carrier case data, and event records.
Practical next step

Tell us about the sites that need to stay online.

Share what's happening and where. We'll recommend the right fix and the next step, starting from your floor plans or site details.

Start your project