It’s never our fault: GoDaddy again
Posted On June 1, 2017
I’m having terrible speeds connecting to my FTP server which I host with GoDaddy. Call tech support, we do a traceroute. They blame COX, my ISP.
Tracing route to ip-107-180-12-113.ip.secureserver.net [184.108.40.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 7 ms 7 ms 6 ms xx.xx.xx.xx
3 7 ms 7 ms 7 ms xx.xx.xx.xx
4 7 ms 8 ms 7 ms xx.xx.xx.xx
5 69 ms 67 ms 68 ms xx.xx.xx.xx
6 68 ms 67 ms 67 ms xx.xx.xx.xx
7 75 ms 75 ms 77 ms xx.xx.xx.xx
8 75 ms 74 ms 76 ms xx.xx.xx.xx
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 74 ms 75 ms 75 ms ip-107-180-12-113.ip.secureserver.net [220.127.116.11]
Everything after #5 are godaddy servers. But you know – gotta follow steps. So I call COX, who basically drop me into endless hold. Well first they told me they couldn’t help me with my router, and that anything that happens after my router connects is not their responsibility. OK whatever.
So lets give old GoDaddy a call again and see what happens this time. Sent them a traceroute. They said hops 9-12 give back a fake result due to their load balancing – that hop 5 is where the problems are starting, which is COX. So I’m too tired to call COX back – we will try it tomorrow.
Did some research, my ping times are fine – today I am back to nice and fast FTP to my host, even though the ping looks exactly the same. Can’t prove, but considering ONLY my godaddy FTP was slow as shit – that it was probably a GoDaddy issue.