A fast download test can coexist with calls that break up or remote sessions that freeze. Start by identifying where the problem appears: one client, one access point, one VLAN, the wired network or the internet connection.
Need help interpreting the results? Request nationwide remote UniFi troubleshooting. Physical cabling and equipment faults may need an on-site visit.
Record the symptom before changing settings
Note the time, affected application, client, connection type and whether other users see the same behavior. Record recent ISP, cabling, gateway or firmware changes. An intermittent problem is easier to investigate when you can correlate symptoms with events.
Compare wired and wireless from the same location
- Test an affected device near an access point, then compare another compatible device.
- If practical, use a wired connection on the same network as a control.
- Compare local connectivity with access to more than one internet destination.
- Repeat during the period when the problem usually occurs.
If wired traffic is healthy while one wireless area struggles, investigate that radio path. If wired and wireless clients fail together, broaden the review to shared switches, the gateway and the WAN. These patterns guide investigation; they do not establish a cause by themselves.
What to check in UniFi
- Wireless clients: signal, retries, channel utilization and whether symptoms follow a particular AP.
- Wired links: unexpected negotiated speeds, port errors, uplinks and known-good patch-cable comparisons.
- Shared capacity: whether upload-heavy work or other activity coincides with the symptom.
- Recent events: device restarts, link changes and changes to the affected network.
UniFi features and navigation vary by version and hardware. See the official WiFi troubleshooting guide and wired-network checks.
Use ping results carefully
Compare the local gateway and multiple destinations, but do not treat a single missed ping as proof of an application outage. Devices can limit or deprioritize ICMP replies. Look for repeatable symptoms and corroborating application, client or link evidence.
Avoid changing several variables at once
Save the configuration, record a baseline and make one justified change at a time. Keep a rollback path. A blind factory reset, broad firewall change or firmware upgrade during business hours can make the original problem harder to diagnose.
Prepare a useful support request
Include gateway/controller model, affected clients, wired-versus-wireless results, approximate timing and recent changes. Use sanitized screenshots and omit passwords, recovery codes and private keys.