OutcomeCX · Network Intelligence · FatPipe WAN Protection

Network Intelligence

Multi-site uptime monitor · FatPipe WAN protection

32Nodes

0Links

0Pkts/s

18msNet lat

4msNet jit

🏪

PAYMENTS / POS18ms/4ms

💳

CARD PROCESSING16ms/3ms

🗂️

PRACTICE / SHOP SOFTWARE20ms/5ms

🛒

ONLINE BOOKING22ms/6ms

☎️

CLOUD PHONES19ms/4ms

🎯

CUSTOMER MESSAGING17ms/4ms

📹

SECURITY CAMERAS21ms/5ms

💾

CLOUD BACKUP15ms/3ms

🔐

VPN / BACK-OFFICE23ms/8ms

🖥️

CHECK-IN KIOSK20ms/6ms

100%

0Disruptions

Network health

Latency

18ms

Jitter

4ms

Pkt loss

0.1%

WEATHER VIEW

Pick a hub to drop a storm on it

A brownout at one hub delays every site routed through it, even sites that look fine.

Storm over

0On time

0Delayed

0Rerouted

Lost so far$0

Kept by FatPipe$0

Tier 1 · Backbone

Tier 2 · Regional

Tier 3 / CLEC

Brand cluster

Disruption

Brownout tracker

1-HOUR SPIKE TRACKER · THRESHOLD >50ms · MULTI-SITE NETWORK

0LAT SPIKES

0JIT SPIKES

0TOTAL

LATENCY

JITTER

SPIKE

SESSION: 00:00:00

REAL-TIME APPLICATION STATUS

What does a network brownout cost you? A brownout is a slow, flaky connection that never fully goes down, so payments, scheduling and customer systems stall without anyone seeing an outage. Start with 20 sites and 5 staff each. Open the conversation with one question: what's your score per Obkio? The goal is 99.99%.

Estimated loss per year

Recovered at goal$0

Per day$0

Per site / year$0

1How many sites?

Type a number, drag the slider, or tap a size.

sites

2What's your score per Obkio?

The opening question. Enter the current Obkio score and the goal, and the calculator works out the time lost to brownouts in between.

Current Obkio score

Share of business hours the connection performs well.

Goal

What FatPipe is built to reach.

Length of each brownout

minutes

Typical length. Only changes how many brownouts it counts, not the total time.

Poor-performance time, per site, per day0 min

Same thing as brownouts per day0

Gap to goal0

?Don't have the score yet?

Don't have the exact numbers? Pick a level. It sets the Obkio score and how much business is lost during a brownout. You can still change any of them below.

3Sales at each site

Pick a site type to fill in typical numbers, then change anything. These are rough estimates, so use your own figures if you have them.

Revenue per site, per day

Average daily revenue of one site ($3,000 a day is about $1M a year).

Open hours per day

hours

Used to turn daily sales into sales per minute.

Fine-tune how much business is lost (optional)

Sales that fail during a brownout

Optional. The cautious/moderate/high setting above fills this in.

Customers who wait or come back

Optional. Share of failed sales that still go through.

Also count customers who never come back (optional)

Include lost customers in the total

Value of one visit

Average spend or billing per visit.

Lifetime value of a customer

What a regular patient or customer is worth over the years.

Never come back after a bad visit

Share of customers hit by a brownout who leave for good.

Sales per minute, per site$0

Share of sales lost during a brownout0%

4Idle staff cost

Staff are paid but can't work while the system is down.

Hourly wage

$/hr

Average pay per employee.

Employees affected

per site

Front desk, techs and others who can't work during an event.

Idle labor per minute, per site$0

5FatPipe cost

Used to show how quickly the loss outweighs the fix.

FatPipe cost per site, per month

$/mo

$150 FatPipe plus a $50 circuit.

Where the loss comes from

Lost sales per brownout

sites × minutes × sales/min × share lost

Idle labor per brownout

sites × minutes × labor/min

Total per brownout

Per day, split

Lost sales per day

Idle labor per day

Lost customers per day

Only counted when switched on in step 3

Adds up to

The daily loss multiplied out, assuming the same brownouts happen every day for all of your sites.

Weekly$0

Monthly$0

Yearly$0

Per site, per day$0

Large retail chains: load their numbers instead

Pick a chain to fill every number above with its profile. You can still change any of them.

All figures are estimates calculated from the numbers you enter.

WHY IT MATTERS FOR SMALL SITES

Dental offices, auto service shops and clinics run on cloud apps: card payments, scheduling or shop software, cloud phones, imaging and backup. With no IT person on site, a short brownout during business hours stalls the front desk and the card terminal at the same time.

HEAD-TO-HEAD: FatPipe WARP vs Cisco Meraki MX

✓ FatPipe WARP

⚠ Cisco Meraki MX

🕐 Failure Detection3 seconds
Active polling every 3s. Catches a brownout before payment and cloud sessions time out.150+ seconds
2.5-min BGP gap. Payment auth fails before failover begins.

⚡ Brownout ResponseSub-second failover
Detects quality degradation — not just hard failure — reroutes before customers notice.No brownout detection
Only acts on hard link failure. Silent degradation = invisible payment failures.

🧾 Front Desk / PaymentsActive-active bonding
Both circuits carry live traffic. Loss of one = no interruption at the front desk.Active-passive only
Failover gap = session drop. Staff must log back in and the card terminal goes dark.

💳 Payment AuthSession preserved via VIP
Virtual IP keeps payment processor connection alive across circuit changes.Auth gap on failover
IP change disrupts payment gateway. Transactions decline until reconnect.

📊 EnterpriseView3-second polling
106-site validation: 5–9 invisible brownout events/site/day. Real multi-site data.No brownout metrics
Dashboard shows green. Site staff and IT have no visibility into degradation events.

💰 Cost Model~$200/site/mo
$150 FatPipe + $50 circuit. Single invoice via EnTelegent.$450–700/site/mo
Meraki licensing + subscriptions + circuits + IT overhead.

FatPipe wins for small multi-location sites
Card payments, cloud scheduling and VoIP cannot tolerate the 150-second detection gap. FatPipe's 3-second polling catches brownouts before they become declined cards and dropped calls. Active-active bonding removes the failover gap, and one invoice covers every site.

SMALL-SITE SCENARIOS

SCENARIO A: Dental office group

Several offices with 5 staff each, cloud practice software, digital imaging and card payments at checkout. A brownout stops the schedule, insurance checks and payment at the same time, and there is no IT person on site. FatPipe keeps a second path live with no staff action.

FatPipe WARP — Clear Winner

SCENARIO B: Auto service shops (Jiffy Lube style)

Many small shops, each with a handful of staff, a cloud work-order system and card terminals. Bays wait on the system, so every minute of brownout is a stalled car and a longer line. One invoice for every site keeps cost and billing simple.

FatPipe Wins on Cost + Reliability

SCENARIO C: Medical clinics

Cloud records, e-prescribing and eligibility checks all depend on a steady connection. FatPipe Virtual IP keeps sessions to payers and processors valid across circuit changes.

FatPipe WARP — Preferred for Cloud Apps

SCENARIO D: 20-site starting pilot

Start with 20 sites, measure brownouts per site for a few weeks, then size the rollout with the ROI Calculator using your real numbers.

Pilot First, Then Scale

THE MERAKI BLIND SPOT — VALIDATED DATA

106-site EnterpriseView deployment revealed 5–9 brownout events/site/day completely invisible to Meraki. For a dental office or auto shop, those brownouts affect card authorization, cloud scheduling and phone quality — delays felt directly at the front desk.

CARRIER OUTAGE STATUS · NETWORK PATHS

NORMAL

DEGRADED

OUTAGE

Press REFRESH to simulate current carrier status

ℹ KEY CARRIER DEPENDENCIES

AT&T (primary for Stop & Shop, Giant, Hannaford) · Comcast Business (Northeast/Mid-Atlantic Stop & Shop) · Lumen/Brightspeed (Food Lion rural Southeast) · Charter Spectrum (mid-market stores) · AIA-B wireless (FatPipe backup, all brands). NC/VA/MD/NE corridor and FL represent highest store density.

AFFECTED BACKBONE NODES

—

01
INTERNET

02
MPLS

03
BGP

04
BROWNOUT

05
FatPipe FIX

FOUNDATION 01THE INTERNET▶

THE INTERNET WAS NEVER BUILT FOR YOUR BUSINESS APPS

Your sites depend on a patchwork of independently owned networks stitched together through business agreements, not engineering. Nobody controls the full route.

When a card terminal hesitates, your scheduling software freezes, or a phone call breaks up — it's rarely a hard failure. It's traffic quietly routed through a congested path that the network considers perfectly acceptable.

HOW TRANSACTION DATA ACTUALLY TRAVELS

KEY DEFINITIONS

Autonomous System (AS)

An independent network operated by a single organization — AT&T, Comcast, a payment processor. The internet is thousands of these passing traffic between each other.

Congestion

When more traffic flows through a path than it can handle. Result: slower delivery, dropped packets, degraded performance — often invisible on monitoring dashboards.

Jitter

Variation in delay between packets. A swing from 10ms to 200ms breaks card payments, cloud software sessions and phone calls intermittently — the hardest problem to diagnose.

🏢 WHY THIS MATTERS FOR SMALL SITES

A dental office or auto shop sends card payments and cloud software traffic over whatever path the carrier and the payment processor choose at that moment. Nobody monitors it for degradation. When congestion builds silently on a busy Saturday morning, card approval slows to 8 seconds and the schedule freezes. Customers wait. Staff call the owner. No alarm. No ticket.

FOUNDATION 02MPLS▶

MPLS WAS THE ANSWER — UNTIL THE CLOUD CHANGED THE QUESTION

Full MPLS at $1,500/site/month is $30K a month for just 20 sites. Your practice or shop software, payment processor, cloud phones and backup are all cloud-hosted SaaS. MPLS can't follow them.

Broadband + FatPipe WAN bonding delivers MPLS-grade reliability at a fraction of the cost — natively compatible with the cloud apps small sites actually use.

MPLS vs PUBLIC INTERNET

FOUNDATION 03BGP▶

BGP KNOWS HOW TO GET THERE. IT HAS NO IDEA HOW WELL.

BGP selects paths based on cost, policy, and network relationships — not latency or packet loss. It answers: can I get there? It never asks: how well?

A customer at the front desk taps a card. BGP picks the path with fewer hops — which is congested. Approval takes 9 seconds. The card declines. No alarm fires. BGP did its job.

BGP PATH SELECTION — THE WRONG CHOICE, MADE SILENTLY

FOUNDATION 04THE BROWNOUT▶

THE OUTAGE YOU NEVER SEE COMING

The circuit is up. The link light is green. The dashboard shows no alerts. But performance has degraded to the point where cloud sessions fail, card approvals stall, and calls drop.

Brownouts are more dangerous than outages because outages get fixed. Brownouts accumulate silently — shift after shift, transaction after transaction — creating lost revenue and walk-away customers with no ticket ever opened.

BROWNOUT vs OUTAGE — WHAT MONITORING SEES vs REALITY

📊 VALIDATED: 106-SITE ENTERPRISEVIEW DATA

3-second polling across a 106-site production network revealed 5–9 brownout events/site/day completely invisible to Meraki and standard monitoring. Dashboards showed green. At a dental office or auto shop, those events affect card approvals, cloud scheduling and phone quality every single day across every affected site.

FOUNDATION 05THE FatPipe FIX▶

ACTIVE-ACTIVE WAN BONDING: THE SOLUTION BGP NEVER HAD

FatPipe WARP monitors all WAN circuits simultaneously — every 3 seconds — and routes traffic in real time to whichever path is performing best. When a brownout begins on the primary circuit, FatPipe is already moving traffic to backup before the card times out, before the schedule freezes, before the front desk notices anything is wrong.

FatPipe WARP — ACTIVE-ACTIVE WAN BONDING

POLLING INTERVAL

vs Meraki 150s

<1s

FAILOVER TIME

vs BGP 150s gap

~$200

PER SITE/MONTH

vs $2K–$8K MPLS

✓ THE COMPLETE SANDLER PARTNERS STACK FOR MULTI-SITE BUSINESSES

FatPipe WARP — active-active WAN bonding, 3s polling, sub-second failover
AT&T Broadband — primary wireline circuit
AIA-B Wireless — always-on backup, eliminates single-carrier transaction risk
EnTelegent EnVision — single-invoice aggregation, one pane of glass

Proven at the 346-site Lendmark Financial rollout. ~$200/site/month ($150 FatPipe + $50 circuit). The model that protects financial branches is even more critical for high-volume retail where every brownout minute equals thousands of lost transactions.

PREPARED BY SANDLER PARTNERS · AUTHORIZED FatPipe NETWORKS CHANNEL PARTNER SINCE 2002

CISCO MERAKI

ACTIVE/PASSIVE

🏪

PAYMENT SESSION — DENTAL OFFICE

Waiting to start...

0:00

--:--Ready. Press START.

FatPipe WARP

ACTIVE/ACTIVE

🏪

PAYMENT SESSION — DENTAL OFFICE

Waiting to start...

0:00

--:--Ready. Press START.

MERAKI — OUTAGE DURATION

—

Session disruption time

FatPipe — OUTAGE DURATION

—

Session disruption time

FatPipe ADVANTAGE

—

Faster session recovery

COMMON OBJECTION

"But Meraki says they have 1-second failover..."

① BEST CASE, NOT TYPICAL

Meraki's 1-second claim is a lab result — clean cut, ideal conditions. Real small sites have gradual brownouts, congested paths, BGP reconvergence. Detection alone takes 3–10 seconds.

⚠ Real sites are not labs.

② 1 SECOND STILL DROPS THE SESSION

A typical card-payment session times out in ~3–5 seconds. Meraki's 1-second gap — best case — consumes 20–33% of that window. In real brownout conditions, the session drops and the terminal goes dark.

✗ 1 second gap = payment session dropped.

③ RECOVERY vs. PRESERVATION

Meraki measures circuit recovery. FatPipe measures session preservation. Ask Meraki directly:

"After failover, does the cashier's active POS session survive?"

🥊

The Bottom Line

If someone punches you in the face and you recover in 1 second, that's impressive. FatPipe is the bodyguard that blocked the punch. The payment session never knew there was a failure.

MERAKI — THE TRUTH

Each session is locked to one circuit. When that circuit fails, the session dies. Payment and cloud software need a persistent connection to the server. An IP change on failover kills it. Staff must log back in and the terminal goes dark. Every time.

⚠ Meraki routes around failure eventually.
Your payment session will not survive the wait.

FatPipe — PATENTED ACTIVE/ACTIVE

FatPipe's 11 patents cover persistent session technology. Sessions ride both circuits simultaneously. Virtual IP / OOIP maintains session state. When one circuit fails, the session was never at risk. The cashier keeps scanning. No re-login. No lane dark. Ever.

✅ FatPipe never knew there was a failure.
Neither did the cashier at lane 12.