stability health
Test Your Internet Stability and Find the Likely Cause
Observe HTTP response times, timing variation and request interruptions, compare public DNS responses, then get a prioritized next step.
Start Connection Check ↓ Choose a Symptom →Measurements describe the endpoint and test shown. HTTP timing is not network-layer packet loss or a direct measurement of your router, WiFi radio or ISP.
Your guided check
60-second request timeline
Start with your symptom
Choose the problem you see. Each path starts with a real observation and the comparison that helps narrow it down.
wifi no internetWiFi Connected but No InternetCheck whether the failure looks device-specific, DNS-related, shared across devices, or limited to particular sites.
disconnectingWhy Does My Internet Keep Disconnecting?Watch this browser’s requests for 60 seconds and see when interruptions are observed. Compare devices and Ethernet to narrow the likely area.
website browser errorsThis Site Can’t Be ReachedCompare your connection with a server-side website check, then separate one-site problems from wider browsing failures.
dnsDNS Server Not RespondingCompare two public DNS-over-HTTPS resolvers and a direct-IP HTTPS endpoint, then check whether the issue follows your browser or network.
slow internetWhy Is My Internet So Slow?Measure a bounded download and compare HTTP response times before and during that transfer. Narrow whether the slowdown follows your device or shared connection.
Start with what your browser can observe
This check sends small, uncached HTTP requests to controlled endpoints. Response times include browser scheduling, connection setup when needed, server processing and the return path. These are HTTP round trips, not ICMP ping or network-layer jitter.
Move from a measurement to a useful comparison
A quiet sample does not exclude an intermittent problem. Compare another device, browser, or Ethernet connection while the symptom is happening. Each comparison adds evidence before we narrow the likely area.
What a health check cannot certify
A browser cannot inspect your router, modem, WiFi radio or ISP equipment. A successful request proves reachability to that endpoint at that time; it cannot certify that every app is working.
Frequently asked questions
Does this measure packet loss?
No. HTTP uses reliable transports. Failed requests and timing variation are not network-layer packet loss.
Can I also check speed?
Choose the slow-internet preset for a bounded download and simultaneous HTTP timing sample. It measures this browser-to-server path, not your broadband plan or upload speed.