Many of our sites - 'this site can't be reached' on AT&T providers

Avatar
  • Answered
We are seeing our sites just fine but many people (mostly with AT&T provider) are getting 'cannot connect to site' error for the majority of our sites.

Chrome message: 'this site can't be reached *websitename* took too long to respond
Safari message: 'safari can't open the page'

Example sites with problem:
achefs.com
salasurbancantina.com

this site however works fine:
wfdentalworks.net

I had one person nslookup & traceroute an affected site on the mac terminal:
** I noticed on the traceroute it says ' Warning: http://salasurbancantina.com/ has multiple addresses; using 198.105.244.130 '

----nslookup ------- (mac)
namehidden$ nslookup http://salasurbancantina.com/
Server: 192.168.1.254
Address: 192.168.1.254#53

Non-authoritative answer:
Name: http://salasurbancantina.com/
Address: 198.105.244.130
Name: http://salasurbancantina.com/
Address: 198.105.254.130

---- traceroute ------- (mac)

namehidden$ traceroute http://salasurbancantina.com/
traceroute: Warning: http://salasurbancantina.com/ has multiple addresses; using 198.105.244.130
traceroute to http://salasurbancantina.com/ (198.105.244.130), 64 hops max, 52 byte packets
1 homeportal (192.168.1.254) 3.107 ms 2.785 ms 2.581 ms
2 172-14-176-1.lightspeed.dllstx.sbcglobal.net (172.14.176.1) 167.770 ms 62.745 ms 7.958 ms
3 71.155.13.102 (71.155.13.102) 6.687 ms 7.051 ms 6.505 ms
4 * 70.143.193.146 (70.143.193.146) 11.870 ms 7.067 ms
5 12.83.80.209 (12.83.80.209) 10.331 ms
12.83.80.233 (12.83.80.233) 9.744 ms
12.83.80.209 (12.83.80.209) 10.333 ms
6 ggr3.dlstx.ip.att.net (12.122.139.17) 9.474 ms 10.670 ms 8.119 ms
7 10ge6-6.core1.dal1.he.net (216.66.78.121) 22.580 ms 22.204 ms 6.311 ms
8 100ge8-1.core1.atl1.he.net (184.105.81.169) 36.550 ms 26.912 ms 26.231 ms
9 100ge11-1.core1.ash1.he.net (184.105.213.70) 46.805 ms 56.437 ms 50.336 ms
10 100ge3-1.core1.nyc4.he.net (184.105.223.166) 46.925 ms 54.213 ms 48.301 ms
11 xerocole-inc.10gigabitethernet12-4.core1.nyc4.he.net (216.66.41.242) 46.379 ms 46.045 ms 46.725 ms
12 * * *
13 * * *


Thank you for your help
Avatar
johnpaulb-imhs1
Hello dwg, Thank you for your question regarding sites not being reachable. In my tests, I was unable to replicate the error. As a test, try using example.com for your domain, instead of http://example.com/. Be sure to replace example.com with your actual domain name. Can you provide the results of a ping test as well for further clues? Thank you, John-Paul