We have several GoDaddy Shared Web Hosting sites.
One of the sites has difficultly downloading large (~100MB) files.
Running a trace routes to the site via Comcast, Verizon and Sprint all result in five request timeouts on GoDaddy equipment behind 184.168.6.81. Perhaps this equipment does not reply to pings, or perhaps it is having issues. Any suggestions as to if anything appears wrong are appreciated.
Trace Route results follow, 107.180.48.??? is the IP address of the Shared Web Hosting having issues.
=============COMCAST====================================================
Tracing route to 107.180.48.???
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 173-162-???-???-miami.hfc.comcastbusiness.net [173.162.???.???]
3 9 ms 9 ms 7 ms 96.120.37.77
4 11 ms 7 ms 8 ms 162.151.128.201
5 8 ms 8 ms 9 ms 69.139.180.238
6 9 ms 14 ms 8 ms ae-17-ar02.stuart.fl.pompano.comcast.net [162.151.2.161]
7 15 ms 13 ms 13 ms 68.86.165.161
8 * 14 ms 13 ms ae13.edge2.miami1.level3.net [4.68.62.149]
9 44 ms 40 ms 40 ms ae-1-11.bear2.washington111.level3.net [4.69.210.178]
10 43 ms 41 ms 43 ms 4.14.98.38
11 42 ms 42 ms 43 ms ip-184-168-6-81.ip.secureserver.net [184.168.6.81]
12 54 ms 42 ms 44 ms ip-184-168-6-81.ip.secureserver.net [184.168.6.81]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 42 ms 42 ms 46 ms ip-107-180-48-???.ip.secureserver.net [107.180.48.???]
=============VERIZON====================================================
Tracing route to 107.180.48.???
over a maximum of 30 hops:
1 6 ms 4 ms 3 ms 192.168.43.1
2 92 ms 79 ms 68 ms 145.sub-66-174-???.myvzw.com [66.174.???.???]
3 124 ms 75 ms 71 ms 67.sub-69-83-106.myvzw.com [69.83.106.67]
4 310 ms 99 ms 78 ms 2.sub-69-83-107.myvzw.com [69.83.107.2]
5 97 ms 73 ms 222 ms 70.sub-69-83-98.myvzw.com [69.83.98.70]
6 258 ms 496 ms 163 ms 112.sub-69-83-96.myvzw.com [69.83.96.112]
7 152 ms 333 ms 162 ms 112.sub-69-83-96.myvzw.com [69.83.96.112]
8 91 ms 71 ms 66 ms 69.sub-69-83-96.myvzw.com [69.83.96.69]
9 108 ms 67 ms 67 ms et-1-1-2.GW18.DFW9.ALTER.NET [157.130.131.9]
10 210 ms 71 ms 69 ms 0.ae2.BR2.DFW13.ALTER.NET [140.222.225.53]
11 687 ms 752 ms * ae8.edge10.dallas3.level3.com [4.68.62.33]
12 * 308 ms 98 ms ae-21-3621.ear1.Chicago3.Level3.net [4.69.141.158]
13 227 ms 102 ms 90 ms 4.53.100.70
14 155 ms 110 ms 109 ms ip-184-168-6-87.ip.secureserver.net [184.168.6.87]
15 115 ms 108 ms 108 ms ip-184-168-6-87.ip.secureserver.net [184.168.6.87]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 226 ms 115 ms 102 ms ip-107-180-48-???.ip.secureserver.net [107.180.48.???]
Trace complete.
=============SPRINT====================================================
Tracing route to 107.180.48.???
over a maximum of 30 hops:
1 2 ms 3 ms 1 ms 192.168.128.1
2 35 ms 120 ms 33 ms ip-68-29-???-???.pools.spcsdns.net [68.29.???.???]
3 * * * Request timed out.
4 95 ms 31 ms 72 ms 66.1.67.13
5 170 ms 161 ms 40 ms sl-crs2-mia-lc1-.sprintlink.net [144.224.115.57]
6 141 ms 94 ms 99 ms 4.68.72.45
7 * * 200 ms ae-21-3621.ear1.Chicago3.Level3.net [4.69.141.158]
8 146 ms 74 ms 106 ms 4.53.100.70
9 98 ms 103 ms 100 ms ip-184-168-6-87.ip.secureserver.net [184.168.6.87]
10 72 ms 79 ms 83 ms ip-184-168-6-87.ip.secureserver.net [184.168.6.87]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 103 ms 74 ms 86 ms ip-107-180-48-???.ip.secureserver.net [107.180.48.???]
Trace complete.
TIA
