Looks fine to me.
Connecting from Florida, USA.
Your server may have been down for maintenance. Or maybe you are dropping out before making it to your website. If we are not using the same path to reach your website, it is possible that you have a bad HOP on the way to your website stopping you from getting to your destination. Run a Trace Route from your location to see how your computer connects to your website.
Turtle posted a neat VISUAL trace tool. Download the lite version (free) and give it a try.
(Copied from my publishing errors page)
The Net is HUGE and you have a lot of distant to get from your machine to your host. Your data has to hop between multiple computers before it makes it to the destination.
A Trace Route command could tell you if there is a delay somewhere between you and the server. Traceing the route helps to identify where the break down occurs. Then provide results to my ISP and my Host for thier comments. Sometimes they can help resolve. No tool needed. Use your DOS command prompt.
Take it to your c drive if you are not already on c
C:\Documents and Settings\Sam>cd c:\ Then type in tracert domainname
C:\>tracert samisite.com See my results from one trace below:
Tracing route to samisite.com [209...xx]
over a maximum of 30 hops:
1 6 ms 7 ms 6 ms 10...x
2 6 ms 9 ms 6 ms pos4-0-0.orldflpnhl-rtr1.cfl.rr.com [24.95.225.169]
3 7 ms 5 ms 6 ms srp1-0.orldflwrpk-rtr1.cfl.rr.com [24.95.224.33]
4 9 ms 9 ms 10 ms 24.95.224.165
5 14 ms 14 ms 13 ms pop2-tby-P0-2.atdn.net [66.185.136.189]
6 14 ms 14 ms 14 ms bb1-tby-P0-3.atdn.net [66.185.138.208]
7 31 ms 36 ms 33 ms bb2-atm-P7-0.atdn.net [66.185.152.245]
8 31 ms 30 ms 34 ms pop1-atm-P4-1.atdn.net [66.185.150.3]
9 32 ms 31 ms 30 ms sl-bb23-atl-10-2.sprintlink.net [144.232.8.209]
10 31 ms 32 ms 32 ms sl-bb21-atl-8-0.sprintlink.net [144.232.12.25]
11 41 ms 33 ms 32 ms 144.232.29.66
12 23 ms 21 ms 22 ms leg-208-30-205-130-RIA.sprinthome.com [208.30.205.130]
13 41 ms 154 ms 176 ms border6.pc1-bbnet1.acs.pnap.net [64.94.0.11]
14 48 ms 48 ms 50 ms itc-3.border6.acs.pnap.net [64.94.6.78]
15 50 ms 50 ms 51 ms suwC5.gig4-3.edeltacom.com [216.154.207.61]
16 49 ms 48 ms 48 ms suw0N.gig4-3-6.edeltacom.com [216.154.207.122]
17 48 ms 48 ms 56 ms 66.0.192.252
18 24 ms 27 ms 24 ms server26.totalchoicehosting.com [209...xx]
Trace complete.
If your trace may end in all timeouts, like this:
13 * * *
14 * * *
15 * * *
If your trace to a system ends in timeouts, and never completes, there could be a problem.
Or if you have other codes, other results than shown above, there could be a problem either sending packets of information TO your host or RECEIVING packets of information FROM your host. Either way, you won't be able to publish (upload information) using CSB, Trellix or FTP with any great reliability until the situation is resolved. Provide copy of trace route results (use copy and paste) to your ISP and/or host to get assistance with interpretation and possibly resolution.
If you can't run a trace route from within your system, NAT (Network Address Translation) is built into most routers now and acts like a firewall. You are basically on a separate local network and assigned and IP by the router and all computers behind the router are protected from the rest of the internet.) Run a test from OUTSIDE your firewall.
To run a tracert use an outside service with your browser, there are lots out there. samspade.org/t/ or tracert.com are reliable.
