An intermittent fault is difficult because the technician may arrive while everything works. A small record of the pattern is often more useful than repeatedly buying replacement equipment. Start by distinguishing a device problem, a local Wi-Fi/network problem and a wider internet or application-service problem without making unauthorised configuration changes.
Record a repeatable pattern
Note date/time, location, device, connection type, affected application and what still works. Does every person lose access, or only one laptop? Does a wired device keep working when Wi-Fi fails? Does the browser reach other services while a single cloud application reports an error? These comparisons narrow the investigation without proving a cause on their own.
Record recent changes such as a moved access point, new device, provider work or an application update. Avoid exposing passwords, full internal network details or customer records in a public ticket. If logs are needed, agree a minimised secure route and authority. An engineer should not need unrestricted access to every business account merely to understand a symptom.
Avoid changing everything at once
Repeated restarts, factory resets and random channel/DNS changes can destroy useful evidence and introduce new faults. Use an agreed bounded diagnostic plan, preserve configuration and know the recovery route before altering it. A router owned or managed by an internet provider or landlord may have restrictions and support dependencies.
A speed test measures a particular path at a particular moment. It does not alone establish coverage, latency, packet loss, application performance or whether a local device is overloaded. Compare observations under stated conditions rather than promise the advertised broadband number will appear everywhere in a building.
Agree investigation and escalation
A useful diagnostic scope identifies what will be checked, the labour cap, evidence/output and when specialist site work or the ISP must take over. Remote support may identify likely local coverage or cabling issues but cannot certify a physical installation it has not tested. Specialist electrical or certified cabling work needs the appropriate competent/insured delivery route.
After a change, retest the actual business task and the conditions which previously triggered the problem. Keep the old/new configuration identity and a safe rollback where applicable. If the fault has not recurred during a limited test, say that; do not declare a permanent resolution without adequate observation.
The best handover records the current hypothesis, evidence, changes, residual uncertainty and next owner. That prevents the next investigation starting again from “the internet is slow” and avoids an unsupported purchase being mistaken for proof of a fix.
Sources and review
Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.
Next review: 4 May 2027