Skip to content

Decision-based WAN monitoring

Stop guessing which WAN circuits need the money.

Most WAN monitoring tools show you traffic. MetricSplit tells you what to do about it: for every circuit, rebalance, right-size, restrict or upgrade, with the evidence and the cost attached.

Multi-vendor by design: built on the NetFlow v9 and IPFIX standards. Supported today: Cisco Catalyst SD-WAN. Rolling out: Fortinet, Palo Alto, Juniper, Meraki and MikroTik. Setup guides. No agent, nothing in the traffic path, and your traffic itself is never touched.

Every circuit gets a verdict

Busiest business-hours moments, measured per direction

Example data
The red line marks 85% Select a circuit to see its evidence

Keep your monitoring tool. Add the decisions.

  • Keep what works. Your monitoring tool tells you when something is down. MetricSplit tells you what each circuit should become.
  • Fast to start. One export setting on each router, or one SD-WAN policy. First findings within days.
  • Clear answers. Every circuit gets a verdict: rebalance, right-size, restrict or upgrade, with the evidence attached.

The problem with WAN spend

WAN bills rise every year

More sites, more cloud, more video. The renewal arrives, and the only option on the table is more bandwidth.

Monitoring shows graphs, not decisions

Utilisation charts tell you a circuit was busy. They don't tell you whether to rebalance it, limit it, shrink it or upgrade it.

Upgrades are decided by guesswork

Without knowing what a circuit is carrying, and whether another circuit already has room, every upgrade is a guess.

See it decide in 20 seconds

A short tour of the dashboard with example data.

  • What every circuit carries: business, neutral (updates, backups, sign-in) or non-business
  • What each circuit costs against what it carries, with the cost attached once you've entered your circuit prices
  • A verdict for every circuit: rebalance, right-size, restrict or upgrade
  • Which sites would be overloaded if one circuit fails
Example dataMore detail: the full 45-second walkthrough →
Business, 456 Mbps (19%) Neutral (updates, backups, sign-in), 120 Mbps (5%) Non-business, 168 Mbps (7%) Idle, 1,656 Mbps (69%)
Example data A 12-site network pays USD 14,200 a month for 2,400 Mbps. At its busiest business-hours moments it uses 31% of it, and USD 994 a month pays for capacity carrying non-business traffic.

Traffic classification: know what every circuit carries

MetricSplit classifies your traffic as business, neutral (updates, backups, sign-in) or non-business such as streaming and social media. You see it by application and by site, in Mbps and in money.

  • By applicationWhich apps fill each circuit at its busiest business-hours moments.
  • By siteEvery site and circuit with its own business, neutral and non-business share.
  • In Mbps and in moneyHow much of the capacity you pay for carries non-business traffic, once your circuit prices are in.
  • Guest Wi-Fi apart from business Coming soonSplit by the guest networks your team confirms, never by a guess.

Limiting non-business traffic doesn't lower the bill on its own. It frees room, and that room is worth money when it avoids an upgrade or lets you move to a smaller plan. MetricSplit shows you which.

Four decisions, each with its evidence

MetricSplit checks the cheapest fix first. A circuit only gets an upgrade verdict when rebalancing and limiting apps can't bring it under 85%, or when even a rebalanced site would still run above 60%: then it says rebalance now and plan an upgrade. Each decision comes with its evidence, and with the cost attached once you've entered your circuit prices.

Rebalance

Move traffic onto a circuit you already pay for. No purchase needed.

Example dataSingapore-R2 is 97% full on download while the other circuit at the same site has room. Balanced, the site runs at 68%.

Right-size

Find circuits that carry almost nothing, and the monthly cost tied up in them.

Example dataThree circuits ran under 1% of capacity in business hours. You see which to check for missing flow export first, and which to price a smaller plan for.

Restrict

Know exactly how much room limiting non-business apps would free, before anyone writes a policy.

Example dataTaking streaming and social media out at New-York-R1 brings it from 47% to 34% full: about 13 Mbps of room at its busiest moments.

Upgrade

Upgrade only the circuits that still need it, and know which direction is the bottleneck.

Example dataRebalancing and limiting apps can't bring this circuit under 85%. Enter the next plan's price and the cost shows up beside the verdict.

Needs action: over 85% Approaching: 60 to 85% Healthy Almost unused Not reporting

Verdicts are marked provisional until a circuit has 30 days of data. You always see how much data a verdict rests on.

If one circuit fails

For every site with two circuits, MetricSplit checks whether the remaining circuit could carry the whole site at its busiest moment. Example data

Singapore

Not resilient

0%Survivor would need 136%

Two 100 Mbps circuits. Upgrading both to 200 Mbps removes the risk.

Hong Kong

Tight

0%Survivor at 88%

It survives, with little headroom at the busiest hour.

London

Resilient

0%Survivor at 52%

Either circuit can carry the site on its own.

The white line on each bar is the surviving circuit's capacity.

Built for real SD‑WAN networks

One router per address and one circuit per router is rarely how a real network looks.

  • Capacity judged per directionDownload and upload are judged separately, so you know which way the bottleneck runs.
  • TLOC extensions and dual-router sites Coming soonTraffic counts against the circuit that physically carries it, and never twice.
  • Several routers behind one public IP Coming soonEach router told apart by its own flow data, not guessed from the address.
  • Traffic riding another site's line Coming soonSee when one site's internet traffic fills a circuit at another site.
Three routers behind one public IP Example: Tokyo has one router, Tokyo-R1 at 100 Mbps. Singapore has two, Singapore-R1 and Singapore-R2 at 100 Mbps each. All three send flow data over MPLS through the data centre, which reaches MetricSplit from a single public IP. MetricSplit will show three separate routers. Tokyo Tokyo-R1 100 Mbps Singapore Singapore-R1 100 Mbps Singapore-R2 100 Mbps Data centre over MPLS One public IP MetricSplit sees 3 routers Tokyo Tokyo-R1 Singapore Singapore-R1 Singapore Singapore-R2
Example data Coming soon Three routers at two sites share one public IP at the data centre's internet exit. MetricSplit will show them as three routers, each with its own circuit and capacity.

What's coming next

Marked here until it's live in the product.

How to start, in three steps

  1. Send your flow data

    Add a flow export on each router, or one cflowd policy in SD-WAN Manager, pointing at MetricSplit. Setup guides.

  2. Confirm your sites

    Your team names the routers, groups them into sites, and enters circuit speeds, costs and business hours in Settings.

  3. Get your decisions

    First findings arrive within days. Verdicts become firm once each circuit has 30 days of data.

  • Metadata only. Flow records about your traffic, no packet contents.
  • Never in your traffic path. Your traffic flows exactly as before.
  • Stored in India. Need another country? Ask us.

Built by a network engineer with 16+ years running enterprise WANs and SD-WAN.

A full security pack for your security team is available on request: hello@metricsplit.com.

Questions

Which routers work with MetricSplit?

Multi-vendor by design: built on the NetFlow v9 and IPFIX standards. Supported today: Cisco Catalyst SD-WAN. Rolling out: Fortinet, Palo Alto, Juniper, Meraki and MikroTik. See the setup guides, and ask us about anything else you run.

Do we need to change anything on our routers?

One export setting on each router, or one SD-WAN policy, that sends flow records to MetricSplit. You'll need to let that export out of your network.

How long until we see results?

First findings arrive within days. Verdicts are marked provisional until each circuit has 30 days of data, so you always know how firm a verdict is.

Does MetricSplit change our network?

No. MetricSplit measures, reports and recommends. Every change is made by your team, in your own tools, when you decide.

Do we have to replace our monitoring tool?

No. Keep it for alerts and uptime. MetricSplit runs alongside it and answers a different question: what each circuit should become, and what it costs you.

Why keep MetricSplit after the first verdicts?

Your WAN doesn't stay still: new apps appear, sites open or grow, circuits get upgraded or replaced, and contracts come up for renewal. MetricSplit judges every circuit again every day, with the evidence attached, so the verdict you act on is always the current one.

Where can MetricSplit run?

Ask us. We'll tell you what fits your security rules.

What does it cost?

The assessment is free. After that, pricing is per circuit per month. Ask us for a quote for your network.

Find out what to do with every circuit

Point your routers' flow export at MetricSplit and see the classification, the decisions and the money for your own network.

Book a free assessment