Case Studies · Outage economics

When the internet dies, payments stop

Multi-site retailers, restaurants, and service businesses live on card transactions. A primary-circuit outage does not just “slow the network” — it freezes POS, online ordering, and loyalty systems across every location that shares that path. Below is the real-world loss-per-minute math, then how redundant site connectivity changes the outcome.

Why minutes matter

Loss per minute when card payments cannot process

Industry research often cites enterprise IT downtime at thousands of dollars per minute. For multi-site payment-dependent businesses, the clearer picture is revenue at the register — multiplied by how many locations go dark at once.

Single busy retail location

~$25–50/min

At $1,500–$3,000/hour in card sales, a 20-minute outage is $500–$1,000 in lost transactions — plus walkouts that never return.

25-location multi-site chain

~$625–1,250/min

Shared-fate WAN or regional ISP failure across all sites: $37,500–$75,000 per hour in payment-dependent revenue alone.

50-location retail network

~$1,250–2,100/min

~$75,000/hour lost sales plus idle labor often pushes direct exposure past $80,000/hour (~$1,400+/min) on a peak Saturday.

Figures are illustrative models based on typical card-heavy sales rates published for multi-location retail and restaurant networks. Your mix of cash, gift card, and offline-capable POS will change the exact number — the scaling problem does not.

Worked scenarios

Multi-site outages, minute by minute

These scenarios model businesses that cannot complete card payments without internet. Each minute offline is revenue that does not ring, labor that still costs, and customers who leave the line.

Multi-site · Food & beverage

18-location restaurant group loses the primary ISP

Lunch rush, Friday. A metro fiber cut takes down the primary circuit at every site on the same regional ISP. POS terminals cannot authorize cards; online ordering and delivery tablets go dark. Cash-only is not realistic for most tables or drive-through.

Assumptions

Locations offline18
Card sales / location / hour (rush)$450
All-site card revenue at risk$8,100 / hr
Outage duration before restore45 min

Loss while payments are down

Loss per minute (all sites)$135
Direct sales lost (45 min)$6,075
Labor still on clock (est.)~$1,100
Direct exposure, one lunch~$7,200
$135 / minute across 18 sites when cards cannot process Same ISP failure pattern often repeats without path diversity
Multi-site · Retail

40 specialty retail stores, Saturday afternoon

A core WAN or payment path failure hits every store. Nearly all volume is card, mobile wallet, or gift card — none of which complete without connectivity. Lines form, carts are abandoned, and social complaints start before IT can open a ticket with the carrier.

Assumptions

Locations offline40
Card sales / store / hour (peak)$1,800
All-site card revenue at risk$72,000 / hr
Outage duration30 min

Loss while payments are down

Loss per minute (all sites)$1,200
Direct sales lost (30 min)$36,000
Idle labor (8 staff × 40 × $20/hr)$3,200 / hr
30-minute Saturday hit~$37,600+
$1,200 / minute payment-dependent revenue only — before brand and recovery cost One half-hour outage ≈ a full day of profit for many mid-market chains
Multi-site · Large footprint

120-location QSR or convenience network

Even a partial regional failure — 30 of 120 sites sharing a carrier path — creates five-figure-per-hour exposure. Full multi-site payment downtime at peak scales into six figures per hour quickly, which is why large retailers often estimate six-figure hourly POS outages on high-volume days.

Partial regional event (30 sites)

Card sales / site / hour$900
Revenue at risk$27,000 / hr
Loss per minute$450
1-hour regional hit$27,000+

Full fleet peak hour (120 sites)

Card sales / site / hour$900
Revenue at risk$108,000 / hr
Loss per minute$1,800
1-hour fleet-wide hit$108,000+
$450–$1,800 / minute depending on how many locations share the failed path Industry reports place some national retail POS outages far higher on peak days
MNSP · Redundant connectivity

Same multi-site footprint, with failover that works

DynaLake designs each site for multi-path internet: a cloud gateway tiered to the location (Cloud Gateway Max, Dream Machine Pro, or Enterprise Firewall Core), plus 5G Backup, Starlink, or both. When the primary ISP fails, card traffic fails over — payments keep processing instead of the register going dark.

Single-path site (typical)

Primary ISP onlySingle point of failure
Card processing on outageStops
40-store Saturday example$1,200 / min lost
30-minute outage cost~$36,000+

DynaLake multi-path site

Primary + 5G and/or StarlinkAutomatic failover
Card processing on primary failContinues
Outage customer impactSeconds of cutover, not stoppage
Same 30-minute ISP eventRevenue protected
Protect the per-minute burn One avoided peak outage often pays for backup paths for years See networking packages →

Simple model you can apply to your fleet

Loss per minute ≈ (average card sales per location per hour ÷ 60) × (number of locations that share the failed path)

  • Use peak-hour card volume, not daily averages — outages hit when traffic is highest
  • Count only locations on the same ISP, SD-WAN hub, or payment path
  • Add idle labor, spoiled inventory, delivery SLAs, and reputation where they apply
  • If offline mode exists, measure how often it actually works under load

Scenarios are representative models for multi-site businesses that depend on internet-connected payment authorization. Actual loss rates vary by ticket size, mix of tender types, and how many sites share infrastructure. Enterprise “all-in” downtime studies often quote higher per-minute figures when including recovery, compliance, and brand impact.

What does a minute of downtime cost your sites?

Share your store count and peak card volume — we will map loss-per-minute exposure and a multi-path connectivity design that keeps payments live.

hello@dynalake.net View offerings