Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

[groppo91]

I am having an issue whereby I can't see my website from BT Broadband but my Three network phone can see it. I have asked friends who are with Virgin Media and they can also not see it. I have been back and forth between godaddy support and BT support and no one can seem to resolve this issue. So far I know that it traces to ip 195.219.194.2 (ripe.net) and then a firewall blocks it to godaddy. I am really not sure what I can do the trace report shows time outs on 2 and 3 however this is apparently normal with BT Broadband.

[smf22]

As BT have said, hops 2 and 3 not responding is normal and nothing to be concerned about.

Where you see time outs after hop 12 is not necessarily a firewall. This is more likely caused by the device at hop 13 not having a 'route' back to the IP address you're sourcing the traceroute from.

Are you able to include the host name or IP address that you're trying to connect to so others using BT IP addresses can see if they see the same behaviour?

[groppo91]

it should be 160.153.162.130 and has a test html so you should see that if everything works but unfortunately its timing out

[smf22 · Accepted solution]

I tried from here with traceroute using ICMP, UDP and TCP and all fail at the same point as you saw.

smf22@lampu:~$ sudo traceroute -I 160.153.162.130
traceroute to 160.153.162.130 (160.153.162.130), 30 hops max, 60 byte packets
 1  erx1 (192.168.1.1)  0.390 ms  0.460 ms  0.536 ms
 2  * * *
 3  * * *
 4  31.55.186.184 (31.55.186.184)  13.058 ms  13.113 ms  13.115 ms
 5  195.99.127.100 (195.99.127.100)  11.904 ms  11.954 ms  11.955 ms
 6  peer5-BE6.telehouse.ukcore.bt.net (213.121.193.175)  14.720 ms  14.269 ms  14.248 ms
 7  t2c4-et-8-1-0-0.uk-lon1.eu.bt.net (166.49.211.248)  11.278 ms  8.164 ms  8.169 ms
 8  ix-ae-33-0.tcore2.LDN-London.as6453.net (80.231.20.1)  8.283 ms  8.330 ms  8.046 ms
 9  * * *
10  if-ae-14-2.tcore2.AV2-Amsterdam.as6453.net (80.231.131.161)  15.472 ms  15.472 ms  16.922 ms
11  if-ae-2-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.5)  16.234 ms  16.113 ms  16.066 ms
12  195.219.194.2 (195.219.194.2)  14.918 ms  14.461 ms  14.975 ms
13  * * *
14  [snip]
30  * * *
smf22@lampu:~$ sudo traceroute -U 160.153.162.130
traceroute to 160.153.162.130 (160.153.162.130), 30 hops max, 60 byte packets
 1  erx1 (192.168.1.1)  0.575 ms  0.569 ms  0.654 ms
 2  * * *
 3  * * *
 4  31.55.186.184 (31.55.186.184)  8.945 ms  8.874 ms  8.873 ms
 5  81.139.57.10 (81.139.57.10)  10.002 ms  11.118 ms  12.109 ms
 6  195.99.127.98 (195.99.127.98)  12.099 ms core4-hu0-6-0-1.faraday.ukcore.bt.net (195.99.127.200)  8.511 ms core3-hu0-8-0-5.faraday.ukcore.bt.net (195.99.127.40)  13.158 ms
 7  host213-121-193-187.ukcore.bt.net (213.121.193.187)  13.124 ms peer1-xe-11-0-0.faraday.ukcore.bt.net (213.121.193.169)  10.743 ms  9.200 ms
 8  t2c4-et-8-1-0-0.uk-lon1.eu.bt.net (166.49.211.248)  8.184 ms t2c4-et-3-3-0-0.uk-lon1.eu.bt.net (166.49.211.246)  9.841 ms t2c4-et-8-1-0-0.uk-lon1.eu.bt.net (166.49.211.248)  10.612 ms
 9  ix-ae-33-0.tcore2.LDN-London.as6453.net (80.231.20.1)  9.491 ms  10.461 ms  9.396 ms
10  if-ae-15-2.tcore2.L78-London.as6453.net (80.231.131.117)  18.767 ms  17.503 ms  15.703 ms
11  if-ae-14-2.tcore2.AV2-Amsterdam.as6453.net (80.231.131.161)  14.784 ms  15.277 ms  15.477 ms
12  if-ae-2-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.5)  17.503 ms  18.864 ms  17.968 ms
13  195.219.194.2 (195.219.194.2)  15.644 ms  14.491 ms  14.704 ms
14  * * *
15  [snip]
30  * * *
smf22@lampu:~$ sudo traceroute -T 160.153.162.130
traceroute to 160.153.162.130 (160.153.162.130), 30 hops max, 60 byte packets
 1  erx1 (192.168.1.1)  0.540 ms  0.538 ms  0.529 ms
 2  * * *
 3  * * *
 4  31.55.186.184 (31.55.186.184)  9.383 ms  9.433 ms  9.326 ms
 5  195.99.127.90 (195.99.127.90)  9.421 ms core3-hu0-16-0-3.faraday.ukcore.bt.net (195.99.127.198)  9.308 ms 195.99.127.98 (195.99.127.98)  9.308 ms
 6  peer1-xe0-0-2.faraday.ukcore.bt.net (213.121.193.185)  10.410 ms host213-121-193-187.ukcore.bt.net (213.121.193.187)  9.738 ms  9.721 ms
 7  t2c4-et-3-3-0-0.uk-lon1.eu.bt.net (166.49.211.246)  9.007 ms t2c4-et-7-3-0-0.uk-lon1.eu.bt.net (166.49.211.234)  8.117 ms t2c4-et-3-3-0-0.uk-lon1.eu.bt.net (166.49.211.246)  8.658 ms
 8  ix-ae-33-0.tcore2.LDN-London.as6453.net (80.231.20.1)  8.084 ms  8.624 ms  8.030 ms
 9  if-ae-15-2.tcore2.L78-London.as6453.net (80.231.131.117)  16.496 ms  16.210 ms  16.005 ms
10  if-ae-14-2.tcore2.AV2-Amsterdam.as6453.net (80.231.131.161)  14.792 ms  15.176 ms  14.770 ms
11  if-ae-2-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.5)  15.490 ms  16.141 ms  16.130 ms
12  195.219.194.2 (195.219.194.2)  14.650 ms  14.945 ms  14.744 ms
13  * * *
14  [snip]
30  * * *

As I'd mentioned previously I suspect this is a routing issue i.e., no return path, rather than a firewall.

The problem is beyond the point of BT's administrative control so there's little that can be done via this forum. I'd suggest contacting GoDaddy and show them that users on BT and VM are not able to connect and have them investigate.

[tvol]

Hi groppo91 - coincidentally I have a domain on that (shared) hosting IP from GoDaddy, and am experiencing the same issues that you are (since some point on Sunday 1st October).

Have bounced between GoDaddy and BT so far - but helpful to know that the issue is more widespread.

https://pulse.turbobytes.com might be helpful - provides traceroutes from a number of global endpoints - and the results indicate that our hosting IP is unavailable from 24/66 of these.

[smf22]

---

@tvol wrote:

Hi groppo91 - coincidentally I have a domain on that (shared) hosting IP from GoDaddy, and am experiencing the same issues that you are (since some point on Sunday 1st October).

Have bounced between GoDaddy and BT so far - but helpful to know that the issue is more widespread.

https://pulse.turbobytes.com might be helpful - provides traceroutes from a number of global endpoints - and the results indicate that our hosting IP is unavailable from 24/66 of these.

---

@tvol. Useful site.... thanks for posting that. With those results I don't see how GoDaddy can try bouncing you back to the ISP. I see failures from Brazil, Canada, Czech Republic, Germany, Denmark, Ireland.... and so the list goes on. Definitely not a BT problem 

[tvol]

Worth noting that GoDaddy claim that tools such as pulse are 'not reliable' as anti-DDOS measures may kick in - not sure I'm completely convinced by that argument...

[groppo91]

Hi tvol thank you I have been bounced back and forth too since sunday... glad to hear you have the same issue its really odd my mobile internet can see it now and again and most of the world can but my uni internet is a no, my bt broadband at home is a no and people on virgin its a no.... I was starting to think I had done something wrong I have only just finished building my new company website and thought hmmm I paid for godaddy I may as well use them then I had no joy going live 😞 ah well probably a matter of waiting a few days and keep logging calls with them

[tvol]

Domains on IP addresses either side of ours appear to be accessible ok... godaddy are claiming that no traffic is reaching them, so are pointing at the transit ISP (Tata appear to own 195.219.194.2). Some mobile/BB networks peer with godaddy in London so don't rely on Tata; these are able to access ok. Oddly I can reach the cpanel for my site, which runs on the same server and uses the same route, but a different IP.

Will let you know if I make any further progress...

[Liam_]

It does seem rather strange. 160.153.162.129 and 160.153.162.131 get the result in the image.  The cpanel link works fine.   While 160.153.162.130   returns this:

The server at 160.153.162.130 is taking too long to respond.

So, it would seem to suggest it's a godaddy problem.