Skip to content
DeviceBench

Free connection check

Am I online? The answer flips as you watch

This page sends no requests at all. It watches the two events your browser fires when a network interface appears or disappears, so the banner changes in the same instant a cable leaves the socket rather than a second later when something times out, and each flip is stamped with the time it happened — which is what an intermittent drop needs before anyone will believe it. Underneath sit the fields Chromium-based browsers publish about the link: the effective-type bucket, a capped downlink estimate and a rolling round-trip figure, each labeled with how it was arrived at. Firefox and Safari publish none of them, and the panel says so rather than showing you zeros.

  • 100% free
  • No signup
  • No requests sent
  • Flips instantly
  • Timestamped drop log

You are online

This device has a network interface with a route on it.

Reading the interface…

Switch Wi-Fi off for two seconds and back on. The banner changes before you have finished the second click, and both moments land in the log below.

Changes while this page has been open

Nothing has changed yet. Leave this tab open in the background while you chase an intermittent drop, and every flip is stamped here with the time it happened.

What the browser will tell you about the link

This browser does not implement the Network Information API, so there is no effective type, downlink or round-trip estimate to show. That is Firefox and Safari behaving as designed rather than a fault, and the banner above works in all of them.

Read the banner as “there is a cable or a radio attached”. A router with no upstream, a hotel portal waiting for a login and a VPN adapter left behind by a closed client all keep it green. To find out whether anything actually answers, the ping test sends real requests and reports what came back.

How to watch a connection drop and come back

Nothing to start; the useful part is what you do with the tab afterwards.

  1. Read the banner

    Green says your device has a network interface with a route on it; amber says the operating system reports none at all. There is nothing to press and nothing to allow — the state is already on screen when the page finishes loading, and the clock beneath it counts how long that state has held.

  2. Prove it works: switch the Wi-Fi off and on

    Turn the radio off for two seconds. The banner changes before you have finished the second click, because the browser fires an event rather than waiting for a request to fail, and turning it back on flips it again just as fast. Both moments are added to the log with the time they happened, which is also the quickest way to confirm the page is genuinely watching rather than showing you a cached answer.

  3. Leave the tab open to catch an intermittent drop

    The complaint that never reproduces on demand is the one this is for. Park the tab on a second monitor for an afternoon and every disconnection is timestamped in a list twelve entries deep. Copy that list into the support ticket: “it drops sometimes” starts an argument, whereas four drops at 14:02, 14:19, 14:47 and 15:03 starts an investigation.

Technical specifications

What is readnavigator.onLine, plus the window online and offline events that change it — no request of any kind is issued
Reaction timeImmediate. The browser raises an event when the interface state changes, so nothing has to time out first
Log depthThe last 12 changes, each stamped with the local clock time it occurred
Extra fieldseffectiveType, downlink, rtt, saveData and connection type, from the Network Information API where it exists
Browser supportChrome, Edge, Opera and Samsung Internet publish the extra fields; Firefox and Safari publish none of them and say so on the panel, while the indicator itself works in all of them
Downlink ceiling10 Mbit/s, rounded to 25 kbit/s — a gigabit line and a 50 Mbit line report the same figure, by design
Data keptNothing. The log lives in this tab, is not written to storage, and is gone when you reload
PriceFree, no signup, and it goes on working while you are disconnected

Frequently asked questions

It says I am online but nothing will load. Which is right?

Both, and this is the exact case the indicator is weakest in. The browser is answering a narrow question — is there a network interface with a route — and a hotel or airport portal waiting for you to accept its terms answers yes to that while blocking everything else. So does a router whose own upstream has died, and so does a home network where the modem is up and the provider is down. If the banner is green and a page will not load, the fault is past your router, and no event-based indicator anywhere can see past your router.

What actually makes a browser report offline?

The absence of any usable network interface, as the operating system sees it — which is a lower bar than it sounds. Pulling the Ethernet cable on a machine with no other adapter does it. Switching off the only Wi-Fi radio does it. What does not do it is losing internet access while an interface remains up, and a surprising number of machines always have one up: a VPN client left running, a virtual switch from a hypervisor, or the adapter a container platform installs all count as interfaces, and they can hold the answer at online while the physical port is unplugged.

Why does Firefox show none of the connection details?

Because the Network Information API is implemented only in Chromium-based browsers — Chrome, Edge, Opera and Samsung Internet. Firefox and Safari have both declined to ship it, largely because effective type, downlink and round-trip estimates add fingerprinting surface for a benefit sites can obtain more honestly by measuring their own performance. The panel says so directly instead of drawing empty rows, and the indicator itself works everywhere, since online and offline events are supported by every browser in current use.

My connection is gigabit fiber, so why does downlink say 10 Mbit/s?

Because that is the highest number the API will ever report. The value is capped at 10 Mbit/s and rounded to the nearest 25 kbit/s deliberately, so that a page cannot use your exact throughput as an identifier, and it is an estimate from recent traffic rather than a measurement of your line. A fiber connection, a fast cable connection and a good office link all report the same ceiling, which makes the field useful for deciding whether to load a large image and useless for comparing plans.

Why does effective type say 3g when I am on Wi-Fi?

Because the label describes recent performance, not the physical medium. The browser sorts what it has been observing into four buckets by round-trip time and throughput, so a fiber line reached through a congested wireless radio can be classified as 3g entirely correctly, and a well-behaved mobile connection is often reported as 4g. The value also lags: a tab that has been idle reports the conditions it last saw, and it settles again after a little traffic.

Does this page keep working when I go offline?

Yes, and that is a side effect of how it is built rather than a feature that had to be added. The page is a static file your browser already has, and the indicator depends on events from the operating system rather than on reaching a server, so the moment you disconnect it carries on running and records the disconnection. Nothing on it needs the network in order to tell you the network is gone.

Does it phone home when my connection changes?

No — this page opens no connection of its own at any point. The banner, the timer and the log are produced from events and clock readings inside the tab, and the drop times you see are never transmitted anywhere. It is the one page in this section that measures nothing, which is precisely what lets it answer instantly.

About navigator.onLine and the honest limits of it

The property behind this indicator is older than most of the web platform and has always promised less than its name suggests. It began as a way to ask whether a browser had been put into an explicit offline mode, and what it means today is narrower than people assume: it is false when the user agent is certain that any attempt to reach the network will fail — no interface, no route — and true the rest of the time. True therefore covers a great deal of ground, including a laptop associated with a café access point that has not yet been paid for, a router whose fiber has been cut, and a desktop whose real adapter is unplugged while a virtual one installed by a VPN or a container runtime keeps the count above zero. The two events that accompany it, fired on the window when that state changes, are what make an instant indicator possible in the first place, and they are also why this page can answer without touching the network.

The extra fields come from a separate specification with its own history. The Network Information API offers a coarse effective type, a downlink estimate, a round-trip estimate and a data-saver flag, and all of them are deliberately blunt: the throughput figure is capped at 10 Mbit/s and rounded, the round-trip figure is rounded to 25 ms and averaged over recent requests rather than measured now, and the effective type is a bucket derived from both. That bluntness is the point — a precise reading of your connection is a fingerprinting signal, which is why Firefox and Safari declined to implement the interface at all and why a page that wants a real number has to measure it for itself. The same instinct shapes everything else a browser will admit to about your machine: core counts are rounded, memory is bucketed, and the device info page lays out which figures are real and which have been softened, while browser info shows the identity string your browser hands to every site you visit. Battery is filtered the same way, which the battery health page has to work around.

So use the banner for what it is good at — catching the moment a link goes away, and proving it happened at 14:02 — and use a real request for the question it cannot answer. Anything that has to know whether the internet is reachable, including this site's own network pages, has to send something and see what comes back. The ping test does exactly that and reports how long the answers took, and the packet loss test sends enough of them at once to show whether the link holds up under pressure. A green banner plus a clean ping run is the pair of readings worth having before you conclude the problem is somewhere else entirely.

What this page sends

Every number on this page is worked out by JavaScript running in the tab you are reading it in. Nothing you type, paste or open is uploaded, logged or kept, which is also why the tools carry on working after you disconnect from the network.

Nothing — and here that is literal rather than a figure of speech. No probe, no beacon and no check-in request is issued at any point, so the only network activity attributable to this page is the one that delivered it to you. The times your connection dropped stay in the tab that recorded them.