Broadband Uptime Monitor

Track connection interruptions and response-time spikes with repeat browser-based HTTPS checks, then export a timestamped dropout log.

Connection stability

Detect Dropouts and Response-Time Spikes

Monitor the connection between this browser and LinkSpeed while this page remains open. Failed requests and spikes can help you document problems, but do not prove your ISP or broadband line is at fault.

Live HTTPS monitor

Track response times and failed requests

Choose how often to check LinkSpeed and a monitoring duration. You can stop any time and export your own timestamped measurements.

Ready

Connection keeps dropping? This monitor shows when an HTTPS check failed, but cannot tell whether the cause is Wi-Fi, the router, your broadband line or the provider. Use the internet dropout troubleshooting guide to interpret the pattern and plan the next test.

HTTPS success rate—Successful requests, not internet uptime
Mean response time—Browser-to-LinkSpeed HTTPS
95th percentile—Response-time variation
Total requests0
Successful / failed0 / 0
Elapsed time0 min

HTTPS response-time timeline

Green: near baseline Yellow: elevated Orange: large spike Red dashed: failed check

Colour thresholds will be set after the first successful HTTPS check. Response time is not ICMP ping.

Thresholds are based on this session's first successful readings, not universal latency grades. Background tabs may be throttled and produce misleading results.

Saved monitoring sessions

Completed or stopped sessions are saved in this browser, up to 12 sessions. Compare failure rates and response times over several runs; sessions are not sent to LinkSpeed's test database.

No saved sessions yet.

Started (local)ChecksFailedSuccessMean95th percentileAction

Select a session in the table before exporting or printing. Browser Print lets you choose “Save as PDF”; this is not a certified ISP fault report. Large sessions keep a representative set of readings for export; summaries retain all checks.

Recent events

  • Events will appear during monitoring.

What the readings mean

How to interpret failed checks and response-time spikes

Compare Wi-Fi against Ethernet

Run a session next to the router over Wi-Fi. If you have an Ethernet-capable device, repeat under similar conditions over Ethernet. Consistently poorer Wi-Fi results point towards a local wireless issue, rather than automatically towards the ISP.

Repeated interruptions

Failure to reach this site might result from your Wi-Fi, router, DNS, ISP, device, mobile fallback, or LinkSpeed hosting. If the fault occurs across several sites and devices, retain your exported CSV and ask the ISP to examine the line and router logs.

Important limitation: This tool checks an HTTPS endpoint on LinkSpeed, not your router, an ICMP echo target, or your entire internet connection. Monitoring only runs with this page open. Hidden or suspended tabs can delay checks. A failed probe is not equivalent to a measured packet-loss percentage, and uptime cannot be guaranteed when the browser sleeps.

Useful follow-up tests

Packet Loss TestLook for delayed and failed browser requests in a shorter controlled run.Loaded Latency TestCheck whether busy uploads and downloads are causing lag.Internet Keeps Dropping?Router, ONT, Wi-Fi and provider fault diagnosis.Wi-Fi Coverage ComparisonRepeat speed tests around the home.

Uptime monitor questions

Does this run 24/7?

No. It is a browser-based monitor. To monitor an unattended line when a PC is off, LinkSpeed would need a separate local agent or external monitoring hardware.

Does a failed check mean my broadband has gone down?

No. It means your browser did not receive a successful LinkSpeed HTTPS response within the timeout. Compare other services and test Ethernet before attributing the cause.

Where is the history stored?

Completed or stopped sessions are saved in this browser (up to 12) until you delete them or clear site data. You can export a CSV or print a session report. Monitoring observations are not submitted to LinkSpeed's results database; normal web-server request logs may still exist.