Home office Wi-Fi and skipping Teams calls

Others reported that the user appeared to skip during Microsoft Teams video calls, alongside slow browsing. Short read-only checks covered three Wi-Fi connections on one PC. They did not measure Teams media health or internet throughput.

Prepared: October 11, 2026 · America/Chicago (CDT)
Investigation window: October 11, 2026. Wi-Fi A: exact time not recorded. Wi-Fi B: 11:40:35–11:41:25 p.m.; repeat 11:41:50–11:42:34 p.m. Wi-Fi C: 11:51:17–11:51:58 p.m. CDT.
Scope: One Windows PC on three Wi-Fi connections labeled A, B, and C. VPN/proxy state, office position, and household traffic were not recorded for each window. No network names or device identifiers are included.

What the evidence suggests

Diagnosis remains undetermined. The public-endpoint replies varied widely on A and between B's two windows. C had quick public-endpoint replies despite a slow gateway reply. These short, uncontrolled checks cannot show whether Wi-Fi caused slow browsing or skipping in Teams.

Confidence: Undetermined: no matched repeat with location, VPN/proxy, and background load recorded; no Teams Call health during a symptom; and no throughput or media test.

Observed evidence

Evidence tables scroll horizontally. Scroll to read all columns, including limitations.

Wi-Fi association readings

Details reported by the Wi-Fi adapter. Signal and link rate do not measure internet quality or throughput.
ID / connection	Band and radio	Signal	Reported link rate	Limit
A-RADIO · A	5 GHz · 802.11ac	74%	866.7 Mbps	Adapter-reported association data; no speed measurement.
B-RADIO · B	2.4 GHz · 802.11n	87%	144.4 Mbps	Adapter-reported association data; no speed measurement.
C-RADIO · C	5 GHz · 802.11ax	90%	1,201 Mbps	Adapter-reported association data; no speed measurement.

Reachability and service checks

RTT is minimum / average / maximum milliseconds among ICMP replies. DNS used the system resolver. TCP checked one HTTPS connection on port 443.
Window	Gateway ICMP	Internet ICMP	System DNS	TCP 443
Wi-Fi A Time not recorded	A-GW 20/20 · 1 / 1.9 / 6 ms	A-INET 20/20 · 10 / 67.9 / 546 ms	A-DNS Resolved · 377 ms	A-TCP Connected · 51 ms
Wi-Fi B · first 11:40:35–11:41:25 p.m.	B1-GW 19/20 · 1 / 2.6 / 15 ms	B1-INET 16/20 · 10 / 221.6 / 950 ms	B1-DNS Resolved · 2,033 ms	B1-TCP Connected · 184 ms
Wi-Fi B · repeat 11:41:50–11:42:34 p.m.	B2-GW 17/20 · 1 / 117.8 / 681 ms	B2-INET 17/20 · 10 / 14.8 / 31 ms	B2-DNS Resolved · 178 ms	B2-TCP Connected · 54 ms
Wi-Fi C 11:51:17–11:51:58 p.m.	C-GW 20/20 · 1 / 16.8 / 302 ms	C-INET 20/20 · 11 / 11.7 / 14 ms	C-DNS Resolved · 527 ms	C-TCP Connected · 62 ms

ICMP echo non-replies are not Teams or application packet loss. A successful TCP connection does not establish media health.

Comparisons and test conditions

These were network-switch snapshots, not a controlled Wi-Fi-only comparison. Switching connections also changed the broader network path. The office position, VPN/proxy state, and background traffic were not confirmed as steady.

A to B: A had consistent gateway replies but a 546 ms public-target maximum. B's first window had slower public replies and service checks; its repeat was much faster to the public target and DNS/TCP service. The B repeat also had slow and missing gateway replies. This variation does not identify a fault boundary.
C: the public target replied in 11–14 ms, while one gateway reply reached 302 ms. A slow gateway ICMP response did not match the public-target replies in this window.
Repeatability: B's two windows disagree. A had no recorded exact time or repeat; C had one short window.

Possible causes

Weak or variable Wi-Fi at the office

Confidence: low. A reported 74% signal and had one slow public-target reply (A-RADIO, A-INET), but its gateway replies were quick and complete. Signal percentage is adapter-specific. The location was not confirmed across networks, and ICMP scheduling or a changed upstream path could explain the outlier. Repeat short gateway and application-health checks from the same spot.

Transient congestion or ICMP-specific delay

Confidence: low. Public and gateway readings changed sharply between B's two short windows; C's gateway outlier did not appear in its public-target replies (B1-GW, B1-INET, B2-GW, B2-INET, C-GW, C-INET). ICMP may be delayed or deprioritized, and household load was not recorded. Repeat with stable conditions and compare app-level readings.

Intermittent name-lookup delay

Confidence: low. The first B lookup took 2,033 ms and the B repeat took 178 ms (B1-DNS, B2-DNS). Other connections also resolved, with different times. The system resolver can use caches or local configuration; no repeated uncached DNS comparison was made. Repeat the same lookup method and compare with the actual browsing symptom.

What remains unknown

The tests did not confirm a common office position, VPN/proxy state, or background traffic across A, B, and C.
Wi-Fi A's exact timestamp was not captured. The reported slow browsing was not reproduced with a measured page-load test.
Teams was not active during the C window; call state during A and B was not confirmed. Teams Call health, media route, and WebRTC relay loss were not measured.
No download/upload capacity, loaded response, or packet-loss profile was run. No site profile was selected. Lower Data is about 3.6 MB and skips upload and relay checks; Full is about 192 MB and may take up to 3 minutes 20 seconds.
ICMP non-replies do not establish application packet loss. The single TCP 443 success on each connection does not test UDP media or guarantee browsing performance.

Recommended next steps

Repeat A, B, and C on this same PC from the confirmed office spot. Keep VPN/proxy and background activity steady, record each timestamp, and take two short windows per connection.
During an affected Teams call, capture Teams Call health for sending, receiving, and video processing. Compare those readings with the time of the symptom.
If transfer capacity or upload pressure remains a question, use the site's Full profile only between calls after accounting for its roughly 192 MB of traffic and up-to-3:20 duration. Lower Data is about 3.6 MB but skips upload and relay checks.
If matched tests still point toward Wi-Fi, compare the same PC near the access point and over Ethernet if available, one change at a time.

Changes and verification

No settings changed. All checks were read-only. No remediation or post-change verification was performed.

Support handoff

No router, access point, provider, or route fault is established, so these readings do not support a targeted escalation yet. If symptoms continue after matched tests, share sanitized timestamps and Teams Call health with the network administrator or provider. Omit Wi-Fi names, account details, and meeting links.

Evidence appendix

Evidence IDs below refer to the summarized observations in this report. Each ping window sent 20 ICMP echo requests to the selected gateway and a public internet target. RTT summaries use replies observed. DNS used the system resolver; TCP tried one HTTPS service connection on port 443. These checks created no bandwidth load.

A-RADIO, B-RADIO, C-RADIO: Windows-reported Wi-Fi band, radio standard, signal percentage, and link rate. Exact association-read time was not retained.
A-GW / A-INET / A-DNS / A-TCP: Wi-Fi A gateway and internet-target ICMP, system DNS lookup, and TCP 443. Exact window time unavailable.
B1-GW / B1-INET / B1-DNS / B1-TCP: Wi-Fi B first window, October 11, 2026, 11:40:35–11:41:25 p.m. CDT.
B2-GW / B2-INET / B2-DNS / B2-TCP: Wi-Fi B repeat, October 11, 2026, 11:41:50–11:42:34 p.m. CDT.
C-GW / C-INET / C-DNS / C-TCP: Wi-Fi C, October 11, 2026, 11:51:17–11:51:58 p.m. CDT. No Teams call was being tested in this window.

Raw command output and network identifiers were excluded from this shareable report. These short probes are snapshots, not a synchronized time series or a complete application test.