TROUBLESHOOTING GUIDE
Why a website keeps disconnecting or loading intermittently
Intermittent loading means conditions are changing between attempts. The problem may be your connection, one browser, part of the website or an upstream service. Compare what fails at the same time and keep a short record; one successful retry does not show that the problem is resolved.
Reviewed
Likely causes
A wireless connection can be unstable. A site can also have an unhealthy server among healthy ones, temporary capacity problems or a failing dependency. Different pages may use different services. These are possibilities to investigate, not conclusions you can draw from a loading spinner. A sign-in session ending is also different from the network disconnecting.
Steps for visitors
Change one thing at a time. Keep certificate warnings, firewalls and other security protections in place. Ask your administrator before changing a managed network.
Record what “disconnecting” means
Note whether the whole page fails, a video stops, a live connection reconnects or you are signed out. Record the exact message, time and page. Wait briefly before one retry.
What the result means: A sign-in problem belongs with account or browser support unless there is evidence of a connection failure. If a payment or submission hangs, check its status before resubmitting to avoid a duplicate action.
Compare failures at the same time
When the problem happens, open an unrelated website. Try the affected page on a second device using the same network, then on mobile data if available.
What the result means: If unrelated sites fail together, start with connection support. If only one service fails across connections, check its official incident page. If one device alone fails, investigate that device or browser. Comparisons made hours apart are less useful because conditions may have changed.
Compare a stable local connection
Where practical, move closer to the router or compare Ethernet on the same internet connection. Keep the test to ordinary browsing rather than repeated downloads.
What the result means: If Ethernet stays reliable while Wi-Fi fails, investigate the wireless link with your router or device support. If both fail together, ask your ISP to examine the connection; it may also be a site-specific problem if other services remain reliable.
Separate a browser problem from a feature problem
Try another updated browser and compare the homepage with the feature that fails. Do not clear all browser data as a first step. If support recommends removing that site’s stored data, save work first and expect to sign in again.
What the result means: A working homepage does not test checkout, streaming or a live session. If only a feature fails, report the feature and action to the website. If only one browser fails, use its troubleshooting guidance while keeping security protections enabled.
Compare a small number of observations
Run a homepage check when the failure occurs, then another after a reasonable interval. Keep the time and result with your browser evidence; avoid rapid repeated checks.
What the result means: A mix of successful and failed observations helps support correlate events, but does not identify the failing component or measure uptime. A checker can miss brief failures or problems specific to your account, region or connection.
Our checker makes a request from our server. It cannot test your Wi-Fi, account or every website feature.
If you own the website
Correlate the reported times with application errors, resource usage, deployments and dependency incidents. Check individual backends behind the load balancer, not just the public homepage. If long-lived connections drop, review application and proxy timeout settings with your hosting provider. Use bounded monitoring with representative transactions and protect customer data in diagnostic logs.
Who to contact
Contact the ISP when multiple services or devices lose connectivity together. Contact the website when its pages or a particular feature fail while other services work; provide times, the action and a redacted error screenshot. Owners should contact hosting or CDN support with relevant error codes and logs when the server path is implicated, and the affected service provider when a dependency fails.
Sources and further reading
These provider documents support the technical explanations. The comparisons above narrow the investigation; they cannot diagnose every network or service.