Helpdesk story

Why is the internet slow at one branch site, and what is using the bandwidth?

To find what is slowing one branch, look at bandwidth by application for that site and compare it with the link size. In this story Omaha is running 212 Mbps of Windows Update across 41 sessions on a 250 Mbps link, which is why everything else crawls. The answer is one screen away instead of several rounds of console filters.

Watch the ticket get answered

Ticket #4482 · Tier 1 · 1:37 PM
Omaha says the internet is crawling. Can someone look?

Still clicking through the console? We already found it.

Hunting in the console

  1. Pick the device group
  2. Open the activity view, wait
  3. Change the time range, wait
  4. Filter by source zone…

Omaha: Windows Update is using 212 Mbps

windows-update 212 Mbps
ms-teams 14 Mbps
ssl 10 Mbps
zoom 6 Mbps

212 Mbps across 41 sessions since 1:02 on the 250 Mbps link.

Bandwidth by application for every site, kept as 5-minute detail for 7 days.

Omahabandwidth by application

Windows Update is using 212 Mbps

windows-update 212 Mbps
ms-teams 14 Mbps
ssl 10 Mbps
zoom 6 Mbps

Link capacity 250 Mbps · 41 sessions · since 1:02 PM

Not an outage. A patch window. Ticket closed in four minutes.

Step by step

Ticket #4482 · Tier 1 · 1:37 PM: “Omaha says the internet is crawling. Can someone look?”

The race: Still clicking through the console? We already found it.

Working through the console means picking a device group, opening the activity view, changing the time range and filtering by source zone, waiting at each step. Firewall Fleet Health shows the answer for Omaha straight away.

  • In the console: Pick the device group; Open the activity view, wait; Change the time range, wait; Filter by source zone….
  • In Firewall Fleet Health: Omaha: Windows Update is using 212 Mbps.

Who and how long: 212 Mbps across 41 sessions since 1:02 on the 250 Mbps link.

Windows Update is using 212 Mbps across 41 sessions since 1:02 PM, on a 250 Mbps link. That one application explains the slow internet.

  • Omaha: Windows Update is using 212 Mbps.
  • 212 Mbps across 41 sessions since 1:02 PM on the 250 Mbps link.

The answer: Not an outage. A patch window. Ticket closed in four minutes.

How Firewall Fleet Health spots this

  • Shows bandwidth by application for every site, kept as 5-minute detail for 7 days.
  • Puts the traffic next to the link size, so you can see when a link is close to full.
  • Shows when the heavy traffic began, so you know how long users have been affected.
  • The Overview shows every firewall at once, so you can see whether one site or many are affected.

Common questions

How do I find what is using the bandwidth at a branch site?

Open the site and read its bandwidth by application. Firewall Fleet Health lists each application with its Mbps, the number of sessions and the time the traffic began, set against the size of the link.

How far back can I look at application bandwidth?

Per-application bandwidth is kept for 7 days of 5-minute detail. Daily link trends go back 13 months.

See your own fleet this way

Explore the demo fleet yourself.

Schedule a demo Explore the live demo (opens in a new tab)