New York, US · 3 carriers · 0 circuits
Infrastructure resilience,
verified.
Stonemark brings your network diagrams, carrier contracts, circuit records, and site data into one place. A consultant reviews it and shows you which resilience claims hold up and which don’t.
Site Inventory
Madrid, ES · 1 carrier · 0 circuits
London, UK · 2 carriers · 0 circuits
Sample data for illustration
HUMAN REVIEW
Software finds the gaps.
People prove them.
Carrier records can be wrong, out of date, or written to make a sale. Before a finding reaches your leadership, a named consultant checks it against the source and makes the carrier back it up.A carrier’s answer is a claim, not proof.
“Diverse routing” is often promised by a sales team. The route records sit with engineering, or with a local access provider the contract never names. Only a formal request gets them.
Documents disagree.
The contract says two paths. The invoice shows one local access provider. The diagram is three years old. Deciding which is true takes an engineer’s judgment, not a keyword match.
Someone has to stand behind it.
A finding can change a budget, a contract, or an audit answer. It should carry the name of the person who checked it, not just a score.
CARRIER VERIFICATION
How a claim becomes a finding.
Request
With your Letter of Authorization (LOA), we ask each carrier for route maps, building-entry points, and conduit records.
Carrier recordsCompare
Routes are overlaid to find a shared conduit, building entry, access provider, or facility.
Route overlayChallenge
Any gap or conflict goes back to the carrier as a specific question that needs a documented answer.
Carrier responseSign off
The consultant publishes the finding with its evidence, their name, and the date.
Signed findingEvery finding shows who checked it, when, and which document backs it up.
EVIDENCE ENGINEERING
What one bad hour costs.
Evidence Engineering is Stonemark’s method: a person checks each resilience claim against carrier records before you rely on it. Compare what that costs with what downtime costs in your industry.- Year one Includes the $10,000 engagement fee
- Average per site Larger estates pay less per site
- Each year after
By industry
This is an illustration, not a forecast or a promise of savings. Stonemark finds and documents gaps; it does not guarantee an outage won’t happen. Industry figures are widely cited averages and your own costs may be higher or lower. Outage types: one location assumes each site carries an equal share of the business; several locations assumes a carrier or shared-route failure that takes out a quarter of your sites; a data center or cloud region assumes everything hosted there stops for every site. Typical lengths are starting points you can change: a data center outage at about 1.5 hours (Ponemon Institute, 2016: $740,357 per incident, $8,851 a minute) and a cloud region at about 7 hours (the AWS us-east-1 outage of December 2021). In Uptime Institute’s 2025 survey, 57% said their most recent major outage cost more than $100,000 and one in five more than $1 million. Sources: Pingdom, average cost of downtime per industry (IT services shown at the midpoint of its $145,000–$450,000 range); ITIC hourly cost of downtime survey; Ponemon Institute, cost of data center outages (2016); AWS post-event summary, December 2021; Uptime Institute annual outage analysis 2025.
EVERYTHING IN ONE PLACE
See what each site depends on
and what fails with it.
Technical details, documents, contracts, and decisions are linked, so you can trace any finding back to its source.Map the infrastructure your business depends on.
Sites, carriers, circuits, services, recovery sites, contracts, and documents are linked so you can follow any dependency.
Two carriers don’t always mean two separate paths.
conduitB
See what’s proven, what’s only claimed, and what’s missing.
- Verified 42
- In review 3
- Missing 2
Three scores show what to fix first.
Each site is scored out of 100 on three questions. The lowest score tells you what kind of fix the site needs, and the fix list is ordered by it.
Is there backup power, more than one carrier, separate routes, and a recovery site in the design?
Low score: change the design.How much of that design is backed by a contract, a carrier record, or a route map, not just a diagram.
Low score: get the missing records.Whether failover to the backup has been tested, and how recently.
Low score: schedule a failover test.In this sample, recovery testing scores lowest, so a failover test is first on the fix list.
CASE IN POINT · SEPT 21, 2026
The backup existed. It just wasn’t there.
The main circuit into the FAA’s Philadelphia radar facility failed. The system switched to its backup fiber, which a construction crew had cut that morning. Flights stopped at Newark, JFK, LaGuardia, Philadelphia, and Teterboro, and about 7,000 flights were delayed or canceled nationwide.Stonemark asks for the evidence.
We check route maps and conduit records.
You get a prioritized list of fixes.
Would your backup pass the same test? See how HA claims are checked
Sources: AP, Reuters, NBC News, FAA statements.
HIGH AVAILABILITY (HA)
You’re paying for high availability.
Have your carriers proven it, or just said so?
Two carriers and two contracts can still share the same local access provider, conduit, building entry point, or facility. If that shared point fails, both connections go down. Stonemark checks the full route for any point they share.Two documented routes. One shared point of failure.
Stonemark checks whether your HA setup matches what you were sold.