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.
- 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.
- 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.
One ticket. One cause. Zero escalations.