# Website not loading: when to wait and when to contact support Source: https://1kapps.com/en/app/site-status/articles/website-not-loading-information-for-support Language: en Publisher: 1kApps Published: 2026-11-02 11:16:48 UTC Updated: 2026-11-02 13:53:44 UTC App: https://1kapps.com/en/app/site-status ![Watercolor of a desk with a laptop, phone, watch and an organized report for support.](https://1kapps.com/uploads/articles/76/cover/c752c05f4f6d59779ca9af82.webp) Before contacting support because a website will not load, find out how widely access is failing. The site may be unavailable across several networks or fail only on the connection you are using. That difference guides the next step: wait, use another network for now or notify the website operator. ## First, check whether only this website is affected Try opening two other websites you normally use. If they work and only one address fails, focus your comparison on that site. If several websites fail too, your internet connection may be affected. That situation is covered further below. ## Compare Wi-Fi, mobile data and an external check 1. On a phone connected to Wi-Fi, open the address that fails. 2. Turn Wi-Fi off and try the same address over mobile data, such as 4G or 5G. Make sure the phone really switched connections. 3. Check the domain with \[Site Status\](https://1kapps.com/en/app/site-status). The request comes from the service’s server, outside your network. Run these checks close together in time. Switching devices while staying on the same Wi-Fi does not test another network. Note whether the site loaded and which message appeared during each attempt. ## It fails on both networks and the external check fails too If the website will not load on Wi-Fi or mobile data and the external check also indicates unavailability, that is strong evidence that the site itself is currently unavailable. The most useful next step is to contact the website’s support team. If you are a visitor, check the service’s official channels for a maintenance or outage notice. If you own the site, send the results to the team that manages it or your hosting provider. Contacting your internet provider is not the first step in this situation. Read the checker’s result carefully: a failed connection and a message saying the check was blocked are different outcomes. Comparing networks strengthens the evidence, but an individual check does not establish an outage for every visitor. ## It works on some networks but not others: start by waiting If the site opens on mobile data or responds to the external check but still fails on your Wi-Fi, it is reachable from at least one network. When other websites work normally and there is no blocking notice, waiting a while and trying again is a reasonable first step. One common explanation is a temporary DNS difference, particularly after domain or hosting changes. DNS finds the website’s address, and different networks can cache information and refresh it at different times. A temporary problem along the connection path is another possibility. The comparison shows where access is failing; it does not, by itself, identify which explanation applies. If you just need to access the site, use the connection that works if possible and retry the original network later. You do not need to start by changing settings or opening a ticket with your internet provider. Access may return without any action from you, although there is no single recovery time. ## When is it still worth contacting support? If the problem persists on subsequent attempts, keeps returning or prevents an important activity, contact the website’s support team and explain which networks work. They can investigate a restriction or persistent fault rather than treating every difference between networks as a general outage. An explicit access-denied or too-many-requests message also needs a different interpretation. Read about \[signs of possible IP blocking\](https://1kapps.com/en/app/site-status/articles/has-website-blocked-my-ip). Advice to wait out temporary instability does not replace investigating a blocking message shown on screen. ## What if several websites fail on the same connection? If several websites fail on Wi-Fi but load over mobile data, the problem is no longer limited to a single website. Check for an interruption notice affecting your connection and whether other devices on that network have also lost access. If the connection problem persists, contacting your internet provider makes sense. ## Then gather the information support needs When there is a reason to open a ticket, send the domain, date, time and time zone, exact error and results from Wi-Fi, mobile data and the external check. Say when it started. A screenshot of the message can help; remove passwords, private links and unnecessary personal information. In Site Status, you can copy the diagnosis or download a PDF to attach to the ticket. The report records the service server’s attempt and should accompany your account of what happened on your own connection. Include your public IP only if support needs it, through a private channel. ## A message template for the website operator Hello\! I am having trouble accessing \[domain\]. Date, time and time zone: \[fill in\] On Wi-Fi: \[loads / fails\] On mobile data with Wi-Fi turned off: \[loads / fails\] External check: \[result and time\] Error message: \[fill in\] When it started: \[fill in\] Could you investigate this access problem? I have attached a screenshot and diagnosis where available. ## Further reading for your situation If you support customers, read \[my website works for me but not for a customer\](https://1kapps.com/en/app/site-status/articles/website-works-for-me-but-not-for-customer). For connection comparisons, see \[a website works on mobile data but not Wi-Fi\](https://1kapps.com/en/app/site-status/articles/website-works-on-mobile-data-but-not-wifi). ## Reference on temporary DNS differences Cloudflare documents how \[DNS record cache lifetimes\](https://developers.cloudflare.com/dns/manage-dns-records/reference/ttl/) affect when users receive updates. This helps explain why different networks may give different results after a change.