Fault isolation

Compare the technician's phone with the customer network.

A phone can show what a user experiences. A local appliance can show what the site experiences. Infracheck combines both views.

When phone-only diagnostics are not enough

A phone may show weak Wi-Fi, captive portal state, DNS latency, or HTTP failure, but it cannot prove whether the whole site is affected. The appliance adds continuous LAN-side evidence from the customer network.

When appliance-only monitoring is not enough

A local appliance may show healthy WAN and DNS, while the technician's phone sees poor signal, sticky roaming, or channel congestion at a specific location. Phone-side checks provide the client-experience view.

Fault isolation examples

• Phone bad, appliance good: likely client-side Wi-Fi, location, device, captive portal, or roaming issue.
• Phone bad, appliance bad: likely site-wide WAN, DNS, gateway, or upstream issue.
• Phone good, appliance bad: possible local infrastructure issue that is not affecting the phone path yet.
• Both intermittent: collect history and reports for support escalation.

Read the network troubleshooting workflow or start with the free appliance.