Systems
Redundant internet connections: two circuits, one trench
A second internet circuit helps only if it shares nothing with the first, and the invoices rarely say whether it does.
Computing America IT. Help desk support, backups and network infrastructure.
Send the two bills
In short
- Redundancy is a property of what two links don't share. Circuits that share a building entry, a trench, a local exchange or an upstream carrier fail together, which is the failure you bought the second one to cover.
- Two companies can sell you two circuits that are the same physical line from the same underlying carrier, and the bill may not say so.
- Downtime multiplies only across independent failures. A failure both circuits share is not multiplied away.
- Until a failover has been exercised, it's an untested claim. In a failover test the switch can work while something behind it, such as the phone system or a site-to-site tunnel, doesn't follow.
- When diversity can't be confirmed, different technology is a reasonable proxy for a different path. A cellular link rarely shares a trench with fiber.
Ask what single event takes both circuits down. If there is one, it sits in one of four shared layers.
The four things a backup link can share¶
| What is shared | The event that takes both down | How to find out |
|---|---|---|
| The building entry | Anything that happens to the one point where cabling enters the building, such as a contractor with a digger | Walk the cabling yourself. You can settle this one without asking anyone. |
| The duct or trench to the street | The same excavation | Ask each provider for a diverse path in writing, specifically for the final stretch to your building |
| The local exchange or cabinet | A power failure or equipment fault at the one facility both services terminate into | Ask which facility each circuit terminates at |
| The underlying carrier | An outage at a company you have no contract with and may never have heard of | Ask each provider whether they own the physical infrastructure or resell someone else's, and whose |
What the arithmetic says, and what it assumes¶
Independent failures multiply. In a worked example, if one circuit is down 1% of the time, two independent ones are both down 0.01% of the time. That gap is what a second circuit buys.
% of the year down
- One circuit1%
- Two independent circuits0.01%
- Two circuits, one trench1%
In this example, if the shared trench causes all of the downtime, two circuits in it are down as often as one.
SourceWorked example, not measured data. It assumes one circuit is down 1% of the year, and that the shared trench accounts for all of that downtime.
The failover nobody has exercised¶
Having two independent circuits and moving traffic between them are separate problems, and the second is where the real defects are. The switch is the easy part. What breaks is everything that assumed the first circuit's address.
- The phone system. Check whether hosted voice or SIP trunks are registered to, or allowlisted on, the primary circuit's address.
- The site-to-site tunnel to another office or a cloud environment, configured against the primary address with no second definition.
- Anything a third party allowlists by address, including payment, EDI and supplier integrations.
- Inbound anything. A backup circuit often carries outbound traffic fine and can't accept a connection.
Find all four the same way: unplug the primary on purpose, at a time you choose, with the staff warned, and then exercise each item: place a call, run a supplier transaction and connect in from outside.
Before and after you sign¶
- 1.Put the table's questions to each provider in writing, so you have a record of what you bought before the outage.
- 2.Ask each provider for the committed restoration time when the circuit fails, and what happens if they miss it.
- 3.Once the second circuit is live, run the failover test above and write down what stopped.
Next step
Send us both circuit bills.
The two invoices, with the circuit identifiers on them. We will tell you what we can establish about whether you are buying one path twice, and give you the specific questions to put to each provider to settle the parts a bill cannot answer.
- Phone
- (214) 723-2510
- Reply
- A person replies, not a sequence: within one business day, from someone who would be on the engagement.
Packages
Start with a package
Four packages, each with its price on the page. Pick one and buy it online.
$199/month
Billed monthly
$182.42/month
Billed yearly
$499/month
Billed monthly
$457.42/month
Billed yearly
- Scammers stopped from sending email as you
- Your website and systems scanned every week
- Your email settings checked every week
- Everything in the 1 to 10 plan
- Covers up to 50 people
$199/month
after a one-time setup fee
- A site planned, designed and built for you
- Hosting and updates every month
$499/month
Billed monthly
$457.42/month
Billed yearly
$999/month
Billed monthly
$915.75/month
Billed yearly
- Your Google profile, fully set up
- A Google post every week
- 2 social posts a week
- Everything in Get found
- 4 social posts a week
- Your top 10 Google searches tracked
from$500/month
after a one-time setup fee
- Your data gathered from the tools you use
- A first analysis that answers your questions
- New findings every month
Related reading
Systems6 min readIT assessment checklist: what to inspect, in order, before switching providers
Five passes, identity to contracts, each read from the systems rather than from the people who run them.
Delivery4 min readMSP exit plan: the handover pack your IT provider should deliver
The nine sections of the pack we commit to hand over at exit, and the two decisions that decide whether any pack is worth having.
Security5 min readOT network segmentation: when the drawing and the switch disagree
The plant network diagram shows a segmented plant. The switch can show a permissive VLAN rule, a two-homed workstation, and a vendor's remote path that isn't on the drawing.
