Evidence and support · 7 min read

Broadband keeps dropping: build a fault log your ISP can use

Record which devices fail, what the router reports and whether Ethernet works. Download a simple log and support template that separate observations from guesses.

1. Record the failure before changing the setup

“The internet went down” can mean a laptop lost Wi-Fi, a meeting app disconnected, a router lost its WAN session or one website stopped responding. Write the visible symptom and exact error first. Note the local time, time zone and approximate duration. If service is still failing, leave the duration open rather than inventing an end time.

Check whether the device remains connected to Wi-Fi or Ethernet. Record the router’s lights or status page in the manufacturer’s terms. A photograph can preserve a short-lived state. If you can safely save relevant logs, do so before restarting, because some equipment clears useful evidence on reboot.

Restore essential service when you need it; collecting evidence should not prevent work or access to urgent communication. Simply record any restart, cable move or fallback connection and the time of that change. A restart that restores service is an observation, not proof of the original cause.

Record the time and symptom, compare another device or Ethernet, save router status and relevant logs, then send support an evidence-based handover.
WireTrace comparison checklist. A method to follow, not a measurement result.
Choose a check for the symptom you see

2. Make one comparison during the same event

A small comparison can narrow the next question
ObservationWhat it suggests checking
Only one device fails; another worksThat device, its app and its local connection.
Several Wi-Fi devices fail; Ethernet worksWireless association, coverage, node or backhaul.
Ethernet and Wi-Fi fail; router reports a WAN eventProvider connection and router WAN logs.
Only one app or website failsThat service, DNS and the application route.

Use another device on the same home connection when possible. A phone using mobile data is a different route, which can be a useful comparison if labelled correctly. Check that the phone has not silently switched from Wi-Fi to mobile data before recording “other device works”.

Do not run several speed tests during a fragile call to gather more numbers. First observe the failure and compare reachability. A later completed speed result describes the recovered connection, not necessarily the missing interval.

3. Understand what monitoring can and cannot establish

A time history can reveal recurring patterns that isolated screenshots miss. thinkbroadband’s Broadband Quality Monitor uses external ICMP probes towards a configured public address. It does not measure every device’s Wi-Fi or the exact path of a video call. A changed address, CGNAT or a router/firewall that does not answer probes can affect the graph.

A solid red ICMP graph is therefore not automatically proof that nobody could browse. Likewise, a clean external graph does not prove an upstairs laptop stayed connected. Do not disable firewall protections just to obtain a prettier graph. Use a monitoring method appropriate to the router and connection, with the owner’s permission.

Device-inventory and event tools such as Fing can add local context when properly installed and configured. Their desktop or agent capabilities are different from a normal webpage. WireTrace’s browser checks do not scan the full LAN or provide continuous background outage monitoring; the log below is a manual worksheet.

4. Keep facts, inferences and changes separate

Use one row for each event. Include the affected task, device, connection and any router observation. Write “not checked” when a comparison was unavailable. An honest gap is more useful than a confident assumption that all devices failed.

Hypothetical log entry: “19:42 local time, laptop call disconnected for about one minute; Wi-Fi icon remained connected; phone on the same Wi-Fi could not open two normally available sites; Ethernet not checked; router status not captured; recovered without a restart.” This is a useful account of observations. It does not claim the ISP caused the event.

If events cluster around a backup, the evening or a device waking from sleep, record that timing and test one controlled change. A correlation is a lead, not a final diagnosis. Avoid deleting older rows after a change: the comparison across configurations is often the most useful evidence.

5. Send a concise support handover

Summarise the recurring symptom, provide a few representative timestamps and describe the strongest comparison. Include the router model, firmware if known, wired or wireless path, and changes already tried. Ask support which additional diagnostic their service needs. The downloadable template keeps this handover short without guessing at a line fault.

Review screenshots and logs before sharing. Remove passwords, Wi-Fi keys, account details and unrelated personal traffic. Provide a public IP or line/account identifier only through the provider’s appropriate private support channel when it is needed.

After a repair or configuration change, repeat the original task during a comparable period and keep recording any recurrence. A successful test immediately after reboot is useful but does not demonstrate that an intermittent problem has gone. The goal is a reliable connection and an evidence trail that makes the next support conversation easier.

Keep the result, not just the impression

Common questions

Does a failed ping prove a broadband outage?

No. The destination, protocol, firewall behaviour and address all matter. Combine a ping observation with the real task, another device and router status; keep each method labelled.

Should I restart the router every time?

Restore service when necessary, but capture relevant lights, status and logs first when practical. Repeated restarts can erase evidence. Follow your provider’s diagnostic instructions and record each restart.

Sources and scope

Browse all connection guides

Questions before you change anything

What should I record when broadband keeps dropping?

Keep time and timezone, outage duration, affected devices and router status. A short consistent record is more useful than a long list of unrelated speed tests.

How do I distinguish a provider dropout from Wi-Fi loss?

Compare wired device, gateway reachability, WAN session and ONT lights. Record which boundary fails; the broadband connection may remain up while one radio client disconnects.

Should I reboot before contacting support?

Save the event log, uptime, error code and status photograph first where safe. Rebooting can restore service but remove the history needed to explain a recurring fault.

Can I use ping results as proof of an outage?

Use them alongside the actual application, test destination, probe interval and device sleep state. An ICMP timeout may reflect filtering or prioritisation rather than general loss of internet service.

What private details should I remove from the fault log?

Redact account numbers, Wi-Fi passwords, public IP addresses and private hostnames unless support specifically needs them through its approved private channel. A public forum does not need your router configuration backup.

Questions and source links reviewed 21 November 2026. The answers apply the limits described in this guide; they are not a test of your equipment.

A notebook used to keep times and observations during a fault
A notebook used to keep times and observations during a fault. AI-generated illustrative scene; not an installation or product-test photograph.
Recording connection symptoms before changing settings — AI-generated scene illustration
Recording connection symptoms before changing settings. AI-generated scene illustration; not a measured result or an exact wiring reference.

Reader questions that informed this update: Reddit: reader discussion · Reddit: reader discussion. Individual reports help identify questions; answers above use the technical references in this guide.

Details worth checking

Should I export router logs before restarting?

If the interface allows a safe export, keep the router logs and their time zone before a restart that may clear them. Redact public addresses, account identifiers and unrelated client details before sharing. A reboot that restores service is a useful recovery observation, but logs from before it may be the only record of the failure.

Explain your own result

Replace the brackets with observations you actually made. Leave unknowns as “not checked”. This draft is written for this guide; it is not a quotation or an automatic diagnosis.

Copying stays on your device. Remove passwords, account numbers and private network details before sharing.

Reader questions that informed this update: Reddit: reader discussion · Reddit: reader discussion. Individual reports help identify questions; answers above use the technical references in this guide.

Keep this guide for the next check

Save the steps and source links for when the connection is unavailable. Your own test results and private network settings are not included.

Source: Broadband keeps dropping: build a fault log your ISP can use. Follow the exact device documentation; illustrative images are not measurements.