Simpler networks. Smaller bills.

ServicesHow we get paidBuckeye CareResultsBlogToolsRefer a businessAboutContactNo charge for a bill auditBook a call614-224-2003
Home / Blog / Networking

What working failover looks like for multi-location businesses

Most businesses think they have failover. The day the main circuit drops, they find out they don't. The difference between a checkbox and a backup that works.

Rings Jonathan and the team 24x7.

9 minRead. Filed under Networking.
2026Published May 26, 2026.
400+Providers we can quote.

We compare prices from 400+ providers and platforms.

AT&TVerizonLumenSpectrumComcastCoxT-MobileFrontierZayoCogentRingCentralNextiva8x8ZoomMicrosoft TeamsWebex

The short version

  • If you haven't tested your failover, you don't have a plan.
  • Real failover: a second path that takes over in seconds, phones that reroute themselves, and a test on the calendar.

The Box and the Contract Are Not the System

A manufacturer in Marion called us last fall. Their primary fiber circuit had been down for forty minutes. The automatic failover they were paying $480 a month for had not kicked in. Three shipping doors were idle. The phones were ringing into a recording. He didn't have failover. He had a box and a contract that mentioned failover. Those are not the same thing.

Most businesses think they have failover. Most don't, at least not in the way that matters. The line item is on the invoice, the router has two WAN ports, and the carrier's portal shows green. Then a backhoe finds a fiber line, or a regional point of presence has an issue, or a backup connection gets shut off for non-payment without anyone noticing, and the failover that was supposed to save the day does nothing.

Real failover is a system with five parts, and you can't buy it as one product. If any part is missing, you're paying for something that won't work when you need it.

The Five Parts of Real Failover

1

Two paths that are physically separate, beyond diverse on paper

Most 'failover' setups are only diverse on paper: two circuits that enter the building through the same conduit, go to the same regional aggregation point and share the same long-haul route. One backhoe takes both down at once. Real physical diversity uses different transport, like a fiber primary with fixed-wireless or bonded LTE as the backup, or two carriers whose entrance facilities you've confirmed come in from different sides of the building. The cost difference is small, and the reliability difference is the whole reason to do it. Where no second cable path reaches the building, Starlink for business is one way to get a truly separate backup.

2

A cutover that happens automatically, and fast

The bad version: the primary drops, someone gets a notification, drives across town and plugs in a backup modem 35 minutes later. That's a disaster-recovery procedure with a stopwatch. The good version uses an SD-WAN appliance or a dual-WAN router that detects the loss within seconds and moves traffic automatically, with total cutover under thirty seconds. The hardware isn't expensive. A capable SD-WAN edge runs roughly five to eight thousand dollars at most sites, and a managed dual-WAN router costs a few hundred plus a service plan.

3

Out-of-band management, so you can see what's happening

When your WAN is down, your remote-management tools are often down too. The cloud controller can't reach the box, and the monitoring dashboard shows everything red. Out-of-band management is a small LTE modem with its own SIM and data plan that keeps the management connection reachable when both the primary and backup WAN are down. You can see device status, see why failover did or didn't kick in, and push a config change instead of guessing.

4

Tested on a calendar, not in a crisis

Networks change all the time: firmware updates, new SaaS dependencies, a rebuilt VPN concentrator. Any of these can break failover that worked the last time you tested it. The fix is a scheduled test. Once a month, disconnect the primary WAN at one site for fifteen minutes and write down what happens. Most businesses have never tested their failover. Of those who have, a good share found something broken on the first test, and each one was an outage caught before it happened for real.

5

The cloud-side blind spot

Circuits can fail over perfectly and the business can still be down, because the failure is upstream. A DNS record with a 24-hour TTL means the world still points to your old address after the cutover. A cloud-hosted PBX with a single SBC in one region goes dark if that region has an issue. Working failover accounts for the cloud side too: short DNS TTLs, multi-region SaaS or a documented fallback, a VPN architecture that fails over with the rest of the WAN, and a SIP carrier with geographically diverse SBCs.

Check These This Week

  • Walk around the outside of your building and find the carrier handhole or meet-me point on two different sides. If you can't, you don't have physical diversity.
  • Ask whoever set up your network how long a cutover takes. If the answer involves a person driving somewhere, it's too long.
  • Put a monthly failover test on the calendar for the same day every month, and treat it like a fire drill.
  • Pull the DNS TTLs on your three most critical public records (web, mail, VPN). Anything over 300 seconds costs you the first hour of every cutover.

Bottom Line

Failover isn't something you buy off a product list. It has five parts: physical diversity, automatic cutover, out-of-band visibility, scheduled testing, and a cloud-side picture that matches what's on site. If any one is missing, the line item on your invoice won't stop the outage. You'll just have a story to tell afterward.

None of this is technically hard, and almost none of it is expensive relative to the cost of an outage. A real failover design at a typical Ohio multi-site business often costs less than the loaded cost of two hours of downtime, once.

The same thinking applies to the room your servers sit in. If it has one circuit, one cooling unit and a few minutes of battery, read when colocation makes sense.

Find out what your failover would do.

We'll map your circuits, test the cutover and tell you in plain terms whether your failover works. There's no obligation.

Book a call