cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Go to solution

Can't route to my Deluxe Linux Hosting with cPanel from my VPS

Hello. I'm having trouble reaching my Godaddy Deluxe Linux Hosting with cPanel (ip 107.180.40.154) from some servers and the blockage appears to me related to Godaddy. I have some Digitalocean VPS in Digitalocean's AMS3 datacenter region (Amsterdam) and the VPS save some backups onto the Godaddy Deluxe Linux Hosting via ftps. The Godaddy Deluxe Linux Hosting's ip is 107.180.40.154, and I can reach it from anywhere else I have tried (including Digitalocean VPS in USA), just not from the VPS in Digitalocean's AMS3 datacenter. Hoping for help/suggestions please. What to do to resolve the issue? Output of ping, traceroute and whois below: Here's a ping attempt:

 

 

$ ping 107.180.40.154
PING 107.180.40.154 (107.180.40.154) 56(84) bytes of data.
From 188.121.32.75 icmp_seq=1 Time to live exceeded
From 188.121.32.75 icmp_seq=2 Time to live exceeded
From 188.121.32.75 icmp_seq=3 Time to live exceeded
From 188.121.32.75 icmp_seq=4 Time to live exceeded

 

 

Here's a traceroute attempt:

 

 

$ traceroute 107.180.40.154
traceroute to 107.180.40.154 (107.180.40.154), 30 hops max, 60 byte packets
 1  * * *
 2  10.82.68.45 (10.82.68.45)  1.306 ms 10.82.68.61 (10.82.68.61)  1.132 ms 10.82.68.31 (10.82.68.31)  1.305 ms
 3  138.197.250.116 (138.197.250.116)  1.608 ms 138.197.250.124 (138.197.250.124)  1.332 ms 138.197.250.110 (138.197.250.110)  1.648 ms
 4  138.197.250.74 (138.197.250.74)  1.119 ms 138.197.250.80 (138.197.250.80)  1.385 ms 138.197.250.84 (138.197.250.84)  1.343 ms
 5  68.142.89.16 (68.142.89.16)  1.511 ms  1.498 ms  1.478 ms
 6  siteprotect.security.neustar (68.142.82.29)  1.652 ms siteprotect.security.neustar (68.142.82.25)  1.372 ms siteprotect.security.neustar (68.142.82.29)  1.105 ms
 7  * * *
 8  * * *
 9  156.154.253.109 (156.154.253.109)  1.207 ms  1.186 ms  1.191 ms
10  ae2.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.5)  1.578 ms  1.589 ms  1.033 ms
11  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  8.014 ms  7.762 ms  7.630 ms
12  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  7.180 ms  7.139 ms  7.104 ms
13  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  7.267 ms  7.089 ms  7.031 ms
14  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  6.655 ms  6.626 ms  6.611 ms
15  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  7.046 ms  7.097 ms  6.737 ms
16  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  12.560 ms  12.544 ms  12.533 ms
17  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  12.263 ms  12.200 ms  12.285 ms
18  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  11.981 ms  11.958 ms  11.943 ms
19  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  15.241 ms  15.231 ms  15.283 ms
20  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  18.141 ms  18.132 ms  18.119 ms
21  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  17.970 ms  17.953 ms  18.071 ms
22  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  17.462 ms  17.452 ms  17.499 ms
23  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  17.996 ms  17.947 ms  17.930 ms
24  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  23.764 ms  23.612 ms  23.594 ms
25  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  27.703 ms  25.020 ms  24.877 ms
26  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  22.982 ms  22.943 ms  22.931 ms
27  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  23.324 ms  23.095 ms  23.118 ms
28  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  28.931 ms  28.913 ms  29.123 ms
29  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  29.580 ms  28.801 ms  28.763 ms
30  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  28.472 ms  28.535 ms  28.516 ms

 

 

The IP address where the traceroute seems to be getting stuck appears to be related to GO-DADDY-NETHERLANDS.

 

 

$ whois 188.121.32.11
inetnum:        188.121.32.0 - 188.121.35.255
netname:        GO-DADDY-NETHERLANDS-BV

 

Why might I be unable to connect? Thanks!

1 ACCEPTED SOLUTION

I wonder if it could be a regional thing? I’m here in the US and didn’t have problems with a CMD: tracert to destination!
-------------------------------------------------------------------------------------------------------------------------------

C:\Users\davis>ping 107.180.40.154

Pinging 107.180.40.154 with 32 bytes of data:
Reply from 107.180.40.154: bytes=32 time=44ms TTL=46
Reply from 107.180.40.154: bytes=32 time=41ms TTL=46
Reply from 107.180.40.154: bytes=32 time=38ms TTL=46
Reply from 107.180.40.154: bytes=32 time=42ms TTL=46

Ping statistics for 107.180.40.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 44ms, Average = 41ms

C:\Users\davis>tracert 107.180.40.154

Tracing route to ip-107-180-40-154.ip.secureserver.net [107.180.40.154]
over a maximum of 30 hops:

1 8 ms 7 ms 8 ms 192.168.1.1
2 16 ms 17 ms 17 ms 072-031-144-033.res.spectrum.com [72.31.144.33]
3 15 ms 25 ms 16 ms 071-044-236-160.res.spectrum.com [71.44.236.160]
4 14 ms 16 ms 16 ms ten12-9-INDP17-AQR1.bhn.net [72.31.202.207]
5 12 ms 15 ms 35 ms 071-044-236-065.res.spectrum.com [71.44.236.65]
6 14 ms 15 ms 15 ms 072-031-203-205.res.spectrum.com [72.31.203.205]
7 12 ms 16 ms 16 ms 071-044-236-048.res.spectrum.com [71.44.236.48]
8 17 ms 17 ms 17 ms 24.27.236.2
9 33 ms 33 ms 43 ms 66.109.5.136
10 51 ms 35 ms 52 ms bu-ether11.nycmny837aw-bcr00.tbone.rr.com [66.109.6.24]
11 31 ms 35 ms 35 ms 66.109.5.119
12 31 ms 35 ms 35 ms 68.142.89.96
13 35 ms 32 ms 32 ms siteprotect.security.neustar [68.142.82.69]
14 43 ms 59 ms 40 ms 156.154.213.134
15 * * * Request timed out.
16 * * * Request timed out.
17 40 ms 44 ms 44 ms 156.154.254.147
18 44 ms 45 ms 44 ms 148.72.36.53
19 41 ms 42 ms 43 ms 148.72.36.44
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 38 ms 43 ms 43 ms ip-107-180-40-154.ip.secureserver.net [107.180.40.154]

Trace complete.

At this point, my best guest would be to reach out to GoDaddy support to see what they think, unless some of the other community members have any other thoughts!

Very Respectfully,

Drew Davis
Navy Veteran and Entrepreneur | GoDaddy Pro user | "Proud to be serving others!"

*** Please note that I offer free advice on this forum. Please feel free to give me KUDOS on this topic/discussion; mark my comment as ACCEPTED SOLUTION if you believe I've helped solved your issue. Thanks! ***

View solution in original post

4 REPLIES 4
davisdre317
Super User 2020

Hello @pandora111 and welcome to the community. I'm a GoDaddy customer like yourself. 

 

Yeah, looking at your tracert, and the whois that you shared, looks like your in the GoDaddy network, but your traceroute seems like it reached its default '30' hops, and is probably longer than '30' hops. 

 

Try the following command, that should extend your hops out to '100':

 

traceroute -m 100 107.180.40.154

 

 

 


Very Respectfully,

Drew Davis
Navy Veteran and Entrepreneur | GoDaddy Pro user | "Proud to be serving others!"

*** Please note that I offer free advice on this forum. Please feel free to give me KUDOS on this topic/discussion; mark my comment as ACCEPTED SOLUTION if you believe I've helped solved your issue. Thanks! ***

Thanks for your reply. Unfortunately extending the hops does not get a different result. Here's the output of traceroute with '-m 100' and ping with '-t 255' as you can see I can't reach the Godaddy server from the VPSes even with the maximum ttl.

 

Any suggestions for what may be causing this or what can I do to get Godaddy to look into the issue?

 

 

ping -t 255 107.180.40.154
PING 107.180.40.154 (107.180.40.154) 56(84) bytes of data.
From 188.121.32.10 icmp_seq=1 Time to live exceeded
From 188.121.32.10 icmp_seq=2 Time to live exceeded
From 188.121.32.10 icmp_seq=3 Time to live exceeded

 

 

 

traceroute -m 100 107.180.40.154
traceroute to 107.180.40.154 (107.180.40.154), 100 hops max, 60 byte packets
 1  * * *
 2  * 10.82.68.61 (10.82.68.61)  0.970 ms *
 3  138.197.250.118 (138.197.250.118)  1.248 ms 138.197.250.100 (138.197.250.100)  14.752 ms 138.197.250.124 (138.197.250.124)  1.133 ms
 4  138.197.250.92 (138.197.250.92)  1.079 ms 138.197.250.88 (138.197.250.88)  1.082 ms 138.197.250.94 (138.197.250.94)  0.945 ms
 5  68.142.89.14 (68.142.89.14)  1.162 ms  1.152 ms  1.137 ms
 6  siteprotect.security.neustar (68.142.82.29)  1.930 ms siteprotect.security.neustar (68.142.82.31)  1.157 ms  1.525 ms
 7  * * *
 8  * * *
 9  156.154.253.109 (156.154.253.109)  1.087 ms  0.852 ms  0.816 ms
10  ae2.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.5)  1.391 ms  1.229 ms  34.268 ms
11  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  2.125 ms  3.302 ms  3.283 ms
12  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  7.365 ms  7.079 ms  7.055 ms
13  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  7.074 ms  12.039 ms  12.073 ms
14  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  7.225 ms  6.778 ms  6.749 ms
15  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  16.086 ms  16.075 ms  16.197 ms
16  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  12.663 ms  12.474 ms  12.450 ms
17  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  13.339 ms  13.244 ms  13.431 ms
18  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  12.043 ms  12.011 ms  11.989 ms
19  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  13.382 ms  13.423 ms  12.365 ms
20  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  18.018 ms  18.005 ms  18.058 ms
21  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  17.823 ms  17.695 ms  20.107 ms
22  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  17.450 ms  17.438 ms  17.336 ms
23  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  19.810 ms  18.989 ms  18.601 ms
24  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  23.535 ms  23.516 ms  23.506 ms
25  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  23.170 ms  23.409 ms  23.236 ms
26  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  22.818 ms  22.800 ms  22.792 ms
27  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  23.422 ms  23.323 ms  23.272 ms
28  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  29.176 ms  29.156 ms  29.135 ms
29  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  29.553 ms  28.698 ms  28.883 ms
30  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  28.303 ms  28.295 ms  28.431 ms
31  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  28.557 ms  28.449 ms  28.578 ms
32  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  34.332 ms  34.395 ms  34.404 ms
33  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  34.171 ms  34.226 ms  34.078 ms
34  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  33.787 ms  33.779 ms  33.840 ms
35  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  34.094 ms  34.071 ms  34.318 ms
36  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  39.742 ms  39.889 ms  39.857 ms
37  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  45.739 ms  41.566 ms  39.758 ms
38  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  39.535 ms  39.173 ms  39.427 ms
39  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  39.393 ms  39.353 ms  39.396 ms
40  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  45.708 ms  45.216 ms  45.558 ms
41  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  44.913 ms  45.848 ms  45.838 ms
42  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  44.635 ms  44.660 ms  44.924 ms
43  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  45.539 ms  45.134 ms  44.823 ms
44  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  50.784 ms  50.796 ms  50.583 ms
45  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  50.634 ms  50.443 ms  50.319 ms
46  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  50.346 ms  50.291 ms  50.682 ms
47  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  50.349 ms  50.480 ms  51.208 ms
48  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  56.248 ms  56.044 ms  56.017 ms
49  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  59.958 ms  56.179 ms  55.935 ms
50  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  55.622 ms  55.611 ms  55.628 ms
51  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  55.739 ms  55.819 ms  56.008 ms
52  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  61.799 ms  61.698 ms  61.478 ms
53  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  61.734 ms  63.231 ms  63.721 ms
54  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  68.462 ms  63.866 ms  64.447 ms
55  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  65.571 ms  65.646 ms  65.766 ms
56  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  67.274 ms  67.145 ms  66.858 ms
57  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  66.817 ms  67.369 ms  67.440 ms
58  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  66.454 ms  66.752 ms  66.646 ms
59  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  69.724 ms  67.229 ms  67.269 ms
60  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  72.755 ms  72.611 ms  72.586 ms
61  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  72.963 ms  72.393 ms  72.188 ms
62  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  72.376 ms  71.875 ms  72.251 ms
63  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  72.056 ms  71.967 ms  72.570 ms
64  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  78.297 ms  78.423 ms  77.848 ms
65  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  91.040 ms  77.668 ms  77.944 ms
66  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  79.358 ms  78.333 ms  77.335 ms
67  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  77.589 ms  77.537 ms  78.537 ms
68  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  83.461 ms  83.328 ms  83.237 ms
69  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  83.459 ms  83.814 ms  83.488 ms
70  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  100.579 ms  86.758 ms  84.436 ms
71  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  83.625 ms  83.120 ms  83.161 ms
72  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  89.402 ms  88.920 ms  89.238 ms
73  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  91.332 ms  88.498 ms  88.824 ms
74  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  88.443 ms  88.299 ms  88.332 ms
75  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  95.450 ms  98.182 ms  98.105 ms
76  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  94.485 ms  94.460 ms  94.439 ms
77  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  97.192 ms  97.467 ms  97.292 ms
78  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  93.592 ms  93.891 ms  93.976 ms
79  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  98.764 ms  98.104 ms  94.317 ms
80  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  100.026 ms  100.207 ms  101.605 ms
81  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  104.030 ms  103.547 ms  104.332 ms
82  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  99.601 ms  99.243 ms  99.223 ms
83  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  99.357 ms  99.329 ms  99.362 ms
84  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  113.799 ms  108.319 ms  108.238 ms
85  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  116.751 ms  105.650 ms  106.810 ms
86  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  104.521 ms  105.241 ms  104.682 ms
87  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  104.937 ms  104.927 ms  104.970 ms
88  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  110.731 ms  111.005 ms  111.101 ms
89  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  111.156 ms  110.449 ms  110.448 ms
90  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  110.473 ms  110.209 ms  110.229 ms
91  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  111.240 ms  111.179 ms  110.194 ms
92  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  116.171 ms  116.067 ms  116.044 ms
93  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  117.734 ms  128.205 ms  123.956 ms
94  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  115.682 ms  116.120 ms  115.410 ms
95  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  115.728 ms  115.630 ms  116.413 ms
96  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  121.669 ms  122.227 ms  121.558 ms
97  ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74)  121.378 ms  122.210 ms  122.062 ms
98  ae3.ams3-bbsa0106-01.bb.gdinf.net (188.121.32.11)  120.930 ms  121.192 ms  120.993 ms
99  ae3.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.10)  132.168 ms  125.080 ms  124.535 ms
100  ae9.fra1-cr-polaris.bb.gdinf.net (188.121.32.75)  128.132 ms  128.091 ms  127.523 ms

 

 

I wonder if it could be a regional thing? I’m here in the US and didn’t have problems with a CMD: tracert to destination!
-------------------------------------------------------------------------------------------------------------------------------

C:\Users\davis>ping 107.180.40.154

Pinging 107.180.40.154 with 32 bytes of data:
Reply from 107.180.40.154: bytes=32 time=44ms TTL=46
Reply from 107.180.40.154: bytes=32 time=41ms TTL=46
Reply from 107.180.40.154: bytes=32 time=38ms TTL=46
Reply from 107.180.40.154: bytes=32 time=42ms TTL=46

Ping statistics for 107.180.40.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 44ms, Average = 41ms

C:\Users\davis>tracert 107.180.40.154

Tracing route to ip-107-180-40-154.ip.secureserver.net [107.180.40.154]
over a maximum of 30 hops:

1 8 ms 7 ms 8 ms 192.168.1.1
2 16 ms 17 ms 17 ms 072-031-144-033.res.spectrum.com [72.31.144.33]
3 15 ms 25 ms 16 ms 071-044-236-160.res.spectrum.com [71.44.236.160]
4 14 ms 16 ms 16 ms ten12-9-INDP17-AQR1.bhn.net [72.31.202.207]
5 12 ms 15 ms 35 ms 071-044-236-065.res.spectrum.com [71.44.236.65]
6 14 ms 15 ms 15 ms 072-031-203-205.res.spectrum.com [72.31.203.205]
7 12 ms 16 ms 16 ms 071-044-236-048.res.spectrum.com [71.44.236.48]
8 17 ms 17 ms 17 ms 24.27.236.2
9 33 ms 33 ms 43 ms 66.109.5.136
10 51 ms 35 ms 52 ms bu-ether11.nycmny837aw-bcr00.tbone.rr.com [66.109.6.24]
11 31 ms 35 ms 35 ms 66.109.5.119
12 31 ms 35 ms 35 ms 68.142.89.96
13 35 ms 32 ms 32 ms siteprotect.security.neustar [68.142.82.69]
14 43 ms 59 ms 40 ms 156.154.213.134
15 * * * Request timed out.
16 * * * Request timed out.
17 40 ms 44 ms 44 ms 156.154.254.147
18 44 ms 45 ms 44 ms 148.72.36.53
19 41 ms 42 ms 43 ms 148.72.36.44
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 38 ms 43 ms 43 ms ip-107-180-40-154.ip.secureserver.net [107.180.40.154]

Trace complete.

At this point, my best guest would be to reach out to GoDaddy support to see what they think, unless some of the other community members have any other thoughts!

Very Respectfully,

Drew Davis
Navy Veteran and Entrepreneur | GoDaddy Pro user | "Proud to be serving others!"

*** Please note that I offer free advice on this forum. Please feel free to give me KUDOS on this topic/discussion; mark my comment as ACCEPTED SOLUTION if you believe I've helped solved your issue. Thanks! ***

View solution in original post

Thanks again for your suggestions. Just to report that the problem seems to have automatically resolved itself for me after about 1 week, and now the servers in question can route to my GD server again (at least they can currently). Unfortunately I don't know then cause of the issue and I didn't manage to get through to Godaddy because their support options seem limited to phone only, and they did not answer the couple of times I tried.