Wi-Fi Performance Crisis? How ZDX Revealed a Hidden Channel Conflict in 15 Minutes

A Real-Time Troubleshooting Case Study for Network Operations Teams

Network Operations (NetOps) teams often face the challenge of troubleshooting intermittent or multi-stage network performance issues. Is the problem local Wi-Fi congestion, a misconfigured access point, or a downstream service routing bottleneck? Without proper visibility, diagnosis becomes guesswork—consuming hours and delaying resolution. Zscaler Digital Experience (ZDX) provides the granular, end-to-end data necessary to move past assumptions and deliver precise, actionable diagnostics with quantifiable results.

We recently observed a prime example of ZDX's operational value when a ZDX administrator deployed the platform to quickly diagnose and confirm resolutions for a dynamic network scenario at a large corporate training event. This case study walks through the real-time diagnostic process, demonstrating how NetOps teams can isolate Wi-Fi configuration issues, validate fixes, and measure the operational impact—all within a single troubleshooting session.

Section 1: Identifying Initial Symptoms & Establishing Baselines

When users report slow performance during peak utilization periods, the first step is to quantify the experience and establish whether the issue is widespread or localized. In this instance, the initial symptoms were:

• Elevated latency reported across the training network SSID (SampleSSID), with readings consistently above the 10 ms target
• User complaints concentrated on specific conference areas, suggesting either AP-level or RF environmental issues
• Scale: 18+ concurrent users on the 5 GHz band, indicating a high-density Wi-Fi scenario

ZDX immediately provided end-to-end visibility into the network path, allowing the engineer to rule out obvious culprits (internet bandwidth, upstream ISP issues) and focus on the local wireless environment.

ZDX Score trending over the 2-hour troubleshooting window. The score dips below 33, indicating degraded application performance during peak training event usage. 

Section 2: Diagnosing Local Wi-Fi Configuration Issues

The real diagnostic power of ZDX lies in its ability to distinguish between different classes of wireless problems. A high latency could stem from poor RF coverage, channel saturation, misconfigured channel assignments, or device overload—each requiring different remediation. The ZDX engineer followed a structured diagnostic approach:

Step 1: Signal Strength Assessment

The engineer checked the wireless signal score across all connected access points. The RSSI (Received Signal Strength Indicator) readings ranged from –44 dBm to –64 dBm, which falls well within the acceptable range (–67 dBm is typically the lower threshold for 5 GHz networks). This indicated strong, consistent RF coverage—ruling out the "weak signal" hypothesis.

Step 2: High Retransmit Analysis

• Good signal strength (RSSI > –65 dBm)
• Low packet loss at the MAC layer
• High retransmit rates

This pattern is a classic indicator of channel interference or channel overlap—not RF weakness.

This dual-chart visualization reveals the diagnostic paradox: despite strong and stable Wi-Fi signal strength (~85%), retransmission rates remain elevated at 35–45%. This pattern is the hallmark of a channel configuration issue rather than RF weakness. High retransmits coupled with strong signal indicates that devices are competing for airtime on congested channels, not struggling with coverage. This insight—captured in real-time by ZDX—immediately pointed the diagnostic team toward channel overlap as the root cause, enabling them to move beyond RF troubleshooting and focus on access point channel assignment optimization.

Step 3: Root Cause Confirmation—Channel Conflict

Source-to-Gateway Latency & Jitter: Morning Volatility vs. Afternoon Stability

Before channel redistribution (morning window), latency and jitter spike to 30–35 ms and 10–33 ms respectively—reflecting MAC-layer contention from the channel conflict. After the fix (11:15 AM onward), both metrics stabilize dramatically: latency settles to 5–10 ms and jitter drops to 5–15 ms range. This 6-hour trending view demonstrates sustained performance improvement, confirming the channel optimization was effective and durable throughout the event.

Section 3: Implementing & Validating the Fix

Remediation: Channel Redistribution

The technical team reconfigured the three APs to use non-overlapping channels:

• AP 1: Channel 36 (5 GHz)
• AP 2: Channel 100 (5 GHz)
• AP 3: Channel 149 (5 GHz)

Resolution Validation: Real-Time Monitoring

Before the Fix:

• Latency: 15–22 ms (Client to Egress)
• ZDX Score: ~72/100 (Okay)
• Retransmit Rate: ~7–9% (elevated)

After Channel Redistribution:

• Latency: 8–12 ms (Client to Egress) — 44% improvement
• ZDX Score: ~87/100 (Good) — 19-point increase
• Retransmit Rate:

Time-series graph showing latency and ZDX score improvements post-remediation. The chart spans the 2-hour monitoring window (10:15 AM–12:15 PM CDT on June 8, 2026) with a clear downward trend in latency after the channel change at approximately 11:00 AM, and a corresponding improvement in the ZDX score. Include threshold lines (10 ms baseline, 85 score target) for reference.

Section 4: End-to-End Path Visibility - Supporting Evidence

While the local Wi-Fi optimization resolved the primary performance issue, ZDX's end-to-end path visibility provided additional context:

Path Analysis Context

The network path from source to the training application endpoint showed:

• Local Wi-Fi to Gateway: 8 ms ✅ (excellent post-remediation)
• Gateway to Egress Point (Las Vegas):
• Egress to Remote Endpoints: 50–70 ms (baseline expectation for geographically distant services)

The Microsoft service endpoints and other cloud applications, while geographically distant, were not the limiting factor in this scenario. The 50–70 ms egress-to-endpoint latency represents normal expectation for cloud services hosted remotely; this is not a bottleneck requiring remediation.

Operational Insight: Clear Diagnostics Enable Confident Decision-Making

This comprehensive path view enabled the NetOps team to:

1. Confirm that local Wi-Fi was indeed the primary constraint (8 ms post-fix vs. 30–35 ms pre-fix)
2. Rule out false leads (remote service latency was not causing the user experience issue)
3. Validate that the application services remain usable despite geographic distance (egress latency is within acceptable bounds)
4. Set realistic expectations for users (local Wi-Fi performance is now optimized; remote service latency is inherent to cloud architecture)

This clarity prevents teams from chasing phantom problems or over-engineering unnecessary solutions.

Conclusion

This scenario showcases ZDX in its operational prime as a diagnostic force multiplier for NetOps teams. By leveraging ZDX's deep, real-time data insights, the engineer was able to:

For NetOps teams managing high-density Wi-Fi environments—whether permanent deployments or temporary events—ZDX transforms troubleshooting from a reactive, time-consuming process into a proactive, data-driven discipline. The combination of granular wireless diagnostics, real-time retransmit monitoring, and sustained performance trending empowers teams to identify and resolve local configuration issues with precision and confidence.

Ready to see with this level of clarity?

See ZDX in Action (Request a Live Demo)