Region you are locating us from: WISCONSIN / USA
Your IP address : 108-255-3-126
Your Internet Service Provider (ISP) AT & T
Able to access Webs.com: NO...site builder message: "Is Site Builder taking too long to load?
Get Troubleshooting Assistance or Refresh Page"
Able to access your live site: NO...NOT THE ENTIRE WEBSITE. HOME PAGE IS VIEWABLE BUT OTHER PAGES TIME OUT
Any specific error messages you're receiving when you view your live site: Problem loading page / The server at
www.hardknottairedales.com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Users\Sue> tracert
www.hardknottAiredales.com
Tracing route to domainsa.freewebs.com [75.98.17.72]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms homeportal [192.168.1.254]
2 20 ms 18 ms 20 ms 108-255-0-2.lightspeed.milwwi.sbcglobal.net [108.255.0.2]
3 21 ms 20 ms 21 ms 71.144.192.180
4 21 ms 20 ms 23 ms 71.144.192.163
5 24 ms 21 ms 23 ms 12.83.79.149
6 30 ms 29 ms 31 ms gar13.cgcil.ip.att.net [12.122.132.121]
7 28 ms 28 ms 28 ms chi-b21-link.telia.net [213.248.87.253]
8 51 ms 51 ms 50 ms nyk-bb4-link.telia.net [62.115.137.58]
9 76 ms 76 ms 76 ms ash-bb4-link.telia.net [80.91.245.98]
10 76 ms 75 ms 77 ms ash-b1-link.telia.net [62.115.122.237]
11 54 ms 57 ms 54 ms neustar-ic-309449-ash-b1.c.telia.net [62.115.51.42]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
If the issue does not lie on our end, based on the traceroute, that is the information I provide. Otherwise, the details are passed to our engineers for further investigation.
This topic was created to get current info from anyone still affected. If you would like further help with this issue, please provide the requested details. Otherwise, the issue cannot be investigated or resolved.
Regardless of where the issue is, we need traceroutes to be able to diagnose where in the connection the issue is occurring so we can fix it. Without traceroutes from people that are affected, the issue can't be fixed.
If you do not have immediate access to all there locations where you encountered the issue, you can provide the details including a traceroute from where you can reproduce the issue right now.
You can then take a screenshot of the results and use the Add Image button above the Reply button at the bottom of this page to insert the image to your reply.
If those instructions are not clear, please let me know your questions and I will answer them.
The traceroute is the single most important information in investigating this issue. The other details help us to gain better insight into your traceroute results, but the traceroute is the key.
I know that progress is hard to see in these support topics. We have used information provided by folks in them to successfully resolve major connectivity issues. The individual cases that remain are significantly more challenging to address, but we are still committed to resolving any connectivity issues that we can for anyone seeing them.
You can also try searching Google for traceroute instructions that may be more accurate.
You'll be running it to the address of the site you cannot see. Once the traceroute finishes running, it will say "Trace complete". Please provide a screenshot of the completed traceroute.
http://www.take-a-screenshot.org/
Please be sure the traceroute was run to your site address.
see the change log
How is this going to help me ANY better than it helped anyone else? aka, it didnt help them and the site still has issues?
Until the issue with your connection is resolved, your site remains up and is able to be accessed by most visitors without any problem.
Did you try using Zenmate as a workaround? https://zenmate.com/
www.freewebs.com/houseofeleganceclothes
www.read-achieve.webs.com