What a failed browser request says about internet health

A page stalls, an upload stops, or your browser reports that a request failed. That can point to a connection problem, but one failed request does not prove your internet service is down. The website, browser, or a brief interruption could also be responsible.

To look for a pattern, use Connection Stability. It measures response time, jitter, lost requests, and dropouts over a few minutes, giving you more context than a single failed page load.

Check whether requests are failing repeatedly

1. Open Connection Stability while connected to the network you want to check.
2. Let the test run for a few minutes. Avoid starting a large download or changing networks while it measures.
3. Look at the results for lost requests and dropouts, along with response time and jitter. These show whether the connection is responding slowly or inconsistently as well as whether requests failed.
4. If you saw a failure on a particular website, try that page again after the test. Note whether the failure happens at the same time as a dropout.
5. Repeat the check once if the result is unexpected. If possible, compare with another device on the same network, or test the same device on a wired connection.

A browser request is a message sent between your browser and a server. If the browser does not get a usable response, it may show a failure. That can happen because the network interrupted the exchange, but it can also happen because the server did not respond, a browser extension blocked the request, or the page itself encountered an error.

What the result means

One page fails, but the stability test has no repeated losses

A single failure is weak evidence of a general internet problem. The website may have been temporarily unavailable, or the browser may have blocked one request. Reload the page and try another site. If other sites work normally, focus on the affected site or browser rather than changing your router settings.

The test shows lost requests or dropouts more than once

Repeated losses mean some requests to the test service did not complete during the measurement. That is evidence of an unreliable path between your device and the test service. It does not identify the cause by itself: the Wi-Fi link, router, internet provider, VPN, or service endpoint could be involved.

Requests complete, but response time or jitter rises

Your connection is responding, but its timing varies or becomes slow. Jitter means response times vary from one request to another. This can make calls, games, and remote work feel uneven even when a page eventually loads. If the delay rises only while someone is uploading or downloading, the connection may be congested.

The test looks stable, but one app or website still fails

The test cannot verify every website or every route across the internet. The affected service, browser settings, an extension, or the app's own connection may be the issue. Try the service in another browser and check whether other devices can reach it.

How to narrow down the cause

1. Repeat the test once. A short interruption can affect one run. If the failures do not return, watch for a recurring pattern before replacing equipment or changing network settings.
2. Check another site and device. If only one site fails, the problem may be specific to that service. If several devices on the same network fail around the same time, the router or internet connection becomes more likely.
3. Pause heavy network use. Stop large downloads, cloud backups, or video streams temporarily, then test again. If the results improve, the connection may be overloaded rather than disconnected.
4. Compare Wi-Fi with a wired connection. If a computer works reliably over Ethernet but loses requests on Wi-Fi, focus on the wireless link or router placement. Browsers cannot read Wi-Fi signal strength in dBm, so this test measures how the connection behaves, not the radio signal directly.
5. Check your network connection. On Windows 11, open Settings › Network & internet and check whether Wi-Fi or Ethernet shows as connected. On macOS, open System Settings › Network and select the active connection. Reconnect to Wi-Fi if it has dropped.
6. Temporarily compare without a VPN. If you are allowed to do so, disconnect the VPN and repeat the test. If the results change, the VPN path may be involved. Keep a work or school VPN enabled if your organization requires it.
7. Restart the router last. If several devices have recurring dropouts, restart the router using its normal power procedure, then test again. If losses continue, contact your internet provider and share when they happen and which devices are affected.

What a browser test cannot prove

Connection Stability checks requests from your browser over a short period. It does not inspect every packet used by every app, measure Wi-Fi radio strength, or prove that a particular router or provider caused a failure. A good result means the test connection behaved well during that run, not that every website will always respond.

For a useful comparison, keep the device and network the same, change one condition at a time, and note whether the failed requests return.