Your Connection — what is my IP and speed test

How to use Connection

Close or pause anything that is downloading, streaming or syncing — it will steal bandwidth from the measurement. Press Start and let the test finish; it reports download, upload and ping together. Run it two or three times and compare. One measurement is a snapshot, not a verdict.

What an internet speed test measures

Download — how fast data reaches you; this governs streaming and page loads. Upload — how fast data leaves you; video calls and cloud backups live here. Ping — the round-trip delay of a single packet; gamers feel every millisecond of it.

Jitter — how much that delay wobbles; a steady 40 ms beats a jumpy 20. Megabits per second, the unit of the first two, counts bits — divide by eight for the megabytes per second your download dialog shows. A surprising share of "my internet is broken" reports dissolve at that division sign.

Getting a number you can trust

Test over a cable when you can — Wi-Fi adds its own losses and then lets the provider take the blame. Test next to the router and then far from it: the difference between the two is your Wi-Fi, not your internet.

Test at different hours. Evenings, when the whole street is streaming, are the honest worst case. Repeat before you complain. A single slow run proves nothing to you or to support. The speed in your contract is a ceiling, not a promise. The test tells you where under that ceiling you actually live.

Reading the results without panic

Numbers below the advertised rate are normal within reason — plans are sold as "up to". What deserves attention is pattern: an online internet speed test showing a steep drop every evening points at congestion, while a constant shortfall on a wired connection points at the line or the plan itself. Keep the results of a few runs; a provider responds very differently to "it feels slow" and to five timestamped measurements.

Intermittent problems

A connection that fails sometimes is harder to fix than one that fails always, because every test you run is likely to pass. The only reliable approach is to record continuously rather than test occasionally — leave something running that logs reachability over time, then look at when the failures cluster. Time of day, a specific device joining, or a regular scheduled task on the network will often show up immediately in that record and never in a spot check.