Helpdesk story

Why does Teams freeze at several branch sites at once?

When Teams freezes at several branches at once, the sites usually share a hub, and the hub is where the loss sits. In this story six complaining sites all hang off the Chicago-DC hub, and its ISP 1 link is dropping 4% of packets since 8:41 AM. Seeing every site, hub and link on one screen turns six tickets into one.

Watch the ticket get answered

Ticket #4471 · Tier 1 · 9:12 AM
Users in Dayton say Teams keeps freezing. Is it just them?

Not just Dayton. Six sites, one cause.

Every complaining site shares one hub, and that hub is where the loss is.

Chicago-DC hub: 4% packet loss on ISP 16 branch sites affected · since 8:41 AM
  • Dayton
  • Akron
  • Lansing
  • Grand-Rapids
  • Joliet
  • Peoria

The loss started at 8:41 and it's only on ISP 1.

Daily and 5-minute history for every public link, so you see when it started and which link it is on.

30 days agoToday 8:41 AM
  • normal
  • packet loss: 1 day

The NOC already knows.

Fleet-wide degradation goes straight to the people who fix it, on the channel they picked.

  • Degraded: Chicago-DC hub, ISP 1 4% loss, 6 sites affected Microsoft Teams · #network-ops · 8:43 AM
  • Same alert Email to on-call engineer email · on-call engineer · 8:43 AM

Tier 1 tells the next caller in ten seconds.

Known issue: Chicago-DC hub ISP 1 degraded Calls and Teams may stutter at 6 sites. Carrier ticket open, next update 10:00. Posted by J. Ruiz, network engineering, 8:55 AM

One ticket. One cause. Zero escalations.

Step by step

Ticket #4471 · Tier 1 · 9:12 AM: “Users in Dayton say Teams keeps freezing. Is it just them?”

Sites and hubs: Not just Dayton. Six sites, one cause.

Six sites report trouble, and all six connect through the Chicago-DC hub. That shared hub is the first place to look.

  • Sites affected: Dayton, Akron, Lansing, Grand-Rapids, Joliet, Peoria.
  • Chicago-DC hub: 4% packet loss on ISP 1. 6 branch sites affected · since 8:41 AM.

Link trend: The loss started at 8:41 and it's only on ISP 1.

The link trend shows packet loss starting at 8:41 AM, on ISP 1 only.

  • Timeline: Today 8:41 AM.

Notify: The NOC already knows.

An alert about the degraded hub reached the NOC channel in Microsoft Teams and the on-call engineer by email at 8:43 AM.

  • Microsoft Teams (#network-ops, 8:43 AM): Degraded: Chicago-DC hub, ISP 1. 4% loss, 6 sites affected.
  • email (on-call engineer, 8:43 AM): Same alert. Email to on-call engineer.

Status banner: Tier 1 tells the next caller in ten seconds.

Network engineering posted a known-issue banner at 8:55 AM, so Tier 1 can answer the next caller straight away.

  • Known issue: Chicago-DC hub ISP 1 degraded. Calls and Teams may stutter at 6 sites. Carrier ticket open, next update 10:00. Posted by J. Ruiz, network engineering, 8:55 AM.

The answer: One ticket. One cause. Zero escalations.

How Firewall Fleet Health spots this

  • Shows every site next to the hub it connects through, so complaints that share a hub stand out.
  • Keeps daily and 5-minute history for every public link, so you can see when the loss started and which link it is on.
  • Sends alerts to Microsoft Teams, Slack, email or SMS, on the channel your team picked.
  • Lets network engineering post a status banner that Tier 1 sees before the next call comes in.

Common questions

How do I tell if several sites share one cause?

Look at the sites and the hubs together. If every site that complains connects through the same hub, check that hub and its links first. Firewall Fleet Health draws the sites and hubs on one screen so the shared hub is visible without opening each firewall.

How do I find out which link is losing packets?

Check the link history for the hub. Firewall Fleet Health keeps daily trends for 13 months and 5-minute detail for 7 days for every public link, so you can see when the loss began and on which link.

How does the network team get told about degraded links?

Alerts go to Microsoft Teams, Slack, email or SMS, whichever channel your team chooses, so the people who fix the problem hear about it before the tickets pile up.

See your own fleet this way

Explore the demo fleet yourself.

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