TL;DR
Most IT and facilities leaders believe they’ve solved for connectivity risk because they have two circuits from two carriers. In a large share of real-world audits, those circuits still converge somewhere — the same building entrance, the same duct bank, the same central office — because nobody traced the physical path past the sales quote. A second contract is redundancy. It is only diversity if an independent field trace proves the two paths never touch. Until that trace happens, the business is paying for two circuits and owns the risk profile of one.
The Status Quo Trap: “We already have two circuits, we’re redundant”
Ask an IT director why their disaster recovery plan assumes continuous uptime, and the answer is almost always some version of: “we have a primary and a backup circuit from two different carriers.” That’s the trap. Two contracts is a procurement decision. Two independent physical paths is an engineering fact — and the two are verified completely differently.
The gap between the two shows up at the worst possible moment. Many businesses that believe they have internet redundancy do not, because they have two circuits running through the same physical conduit, or two connections from the same carrier. It’s common for both services to originate from the same carrier, use the same conduit entering the building, rely on the same regional backbone, or ultimately depend on the same upstream transport provider. On paper, the architecture diagram shows two lines into the building. In the ground, it’s one duct bank with two cables in it.
The FCC drew this exact line more than a decade ago and has kept sharpening it since. In its 2013 911 reliability order, the Federal Communications Commission made the distinction unusually clear: logical diversity can mean different transmission equipment while the circuits still share a fiber or conduit, while physical diversity means sufficient route separation that one power failure, equipment failure, or cable cut does not disable both. The FCC’s 911 reliability rules add that circuits sharing a common segment, such as one fiber cable, don’t count as physically diverse even when they are logically separate. That rule exists because carriers kept selling — and buyers kept accepting — “diverse” circuits that weren’t.
The real alternative isn’t switching carriers again. It’s treating physical path verification as a standing line item in every WAN renewal and every new-site build — not a one-time question asked during the sales call and never revisited.
The Tele Data Guru Framework: The Physical Diversity Verification Matrix
“Diverse” is a word carriers use loosely. Before signing or renewing a dual-circuit WAN design, score each diversity claim against what it actually protects — and how hard it is to verify.
| Diversity Claim | What It Actually Guards Against | Where It Commonly Breaks Down | How to Verify |
|---|---|---|---|
| Carrier Diversity (two providers) | One vendor’s business or equipment failure | Both providers resell the same incumbent’s last-mile fiber or share a POP | Ask for the underlying last-mile carrier name, not just the billing entity |
| Circuit Diversity (two circuit IDs, one provider) | A single card or port failure | Both circuits still ride the same fiber sheath or the same conduit | Request OTDR test results and fiber sheath IDs, not just circuit IDs |
| Route Diversity (separate paths on a map) | A single cut along one documented path | Paths converge at the building entrance, a shared manhole, or a bridge crossing | Independent field trace of KMZ data, verified on-site — not read off a PDF |
| Facility / POP Diversity | A regional outage at one central office or data center | Routes terminate in the same meet-me room or central office | Confirm the physical floor and room of termination, not just the facility name |
The pattern across real audits is consistent: the last mile, the building entrance, the central office, and resold access are the four places where separate-looking circuits tend to meet. Most procurement teams stop at carrier diversity — different logos on two invoices — and never get to route diversity, which is the layer that actually determines whether a backhoe takes down one connection or both.
The Correlated Outage Exposure Formula
Correlated Outage Exposure = (Revenue or Operating Cost per Hour of a Full Outage × Expected Hours to Restore a Shared-Segment Failure) − Cost of a One-Time Physical Route Verification
Example: a multi-site healthcare network calculates $18,000/hour in lost clinical system access and billing capacity during a full outage. A shared-conduit cut that takes out both “redundant” circuits at once averages 6 hours to restore, because the fix is a single physical repair crew, not a carrier failover switch — that’s $108,000 of exposure sitting behind an assumption nobody tested. An independent physical route verification audit for that same site runs roughly $5,000–$8,000. The math isn’t close, and it’s the number that gets a route audit onto a CFO’s agenda instead of staying a network engineer’s hunch.
Commercial Realities & Vendor Pitfalls
- Carriers legally can’t hand you a competitor’s full route map. Carriers cannot share fiber cable route details with other carriers, and it can be difficult for enterprises to obtain KMZ files with enough detail from all involved carriers to independently ensure diversity. That’s not an oversight you can fix by asking nicely — it requires a third party to trace both paths independently.
- The convergence point is almost never where you’d guess. Carrier maps stop at the boundary of each carrier’s own network, KMZ files rarely carry enough resolution, and the convergence point is almost always in the last few hundred meters — the shared duct bank, the common pit, the single lead-in. Desk review alone will not catch this.
- Diversity sold at install doesn’t stay diverse. Carriers reroute fiber for their own maintenance and capacity needs after your circuits are live, and few contracts require them to notify you or re-certify the separation when they do.
- “Diverse” entry points still share the last few hundred feet. Two separate carriers, two separate contracts, and two separate circuits can still rely on the same physical entrance path into the building — and if that entrance is impacted, both services can fail together.
- Industry minimum-separation standards exist — most contracts don’t reference them. BICSI’s Telecommunications Distribution Methods Manual recommends maintaining at least 25 feet of physical separation between diverse pathway runs within a facility to mitigate common-cause failures from fire, flooding, or physical intrusion. Few enterprise WAN contracts cite this standard or hold the carrier to it.
Implementation Checklist
- Identify every site where a single outage would halt revenue-generating or life-safety operations — this is where a physical trace pays for itself fastest.
- Request KMZ route files and OTDR fiber-sheath test data from every carrier serving that site, not just circuit IDs and SLAs.
- Commission an independent field trace of both paths rather than relying on carrier-provided route maps alone.
- Confirm building entrance, riser, and central office/meet-me-room assignments for each circuit individually.
- Add a contractual re-verification clause requiring carriers to disclose route changes and re-certify diversity after any reroute.
- Run a planned, carrier-coordinated failover test — not just a desktop exercise — to confirm the secondary path actually carries production traffic under failure conditions.
- Re-audit route diversity on a fixed schedule (annually, or at renewal) since diversity drifts silently as carriers reroute infrastructure over time.