traceroute is another tool used by the pros to diagnose network problems.
It asks the question, “What is the route used to get there, and what are the road conditions
like along the way?”
In other words, traceroute will give you information about the condition
of the connection between your computer and your FTP server. Think of it like
Google Maps or Mapquest
directions for data.
For more information about traceroute:

To use tracert on Microsoft Windows, you'll need to open the command line (this used to
be called a DOS prompt):
CMDtracert your-account.exavault.com
After you've entered the command, you should see responses like those in the picture below. If you see asterisks, that means that a router or server along the way didn't respond.
Note that when you traceroute to your ExaVault server, our firewalls may not send responses back.
If the last lines in the tracert list asterisks instead of a server and response times,
don't worry about it. Use Ping to test connectivity to the server.

Copying text from the Windows Command Prompt isn't like copying text from any other Windows program. To copy the test from the Windows command prompt:
Enter key on the keyboard.
You should now be able to paste the results of the tracert into an email.

Using traceroute in Mac OS X is really easy:
traceroute your-account.exavault.com
After you've entered the command, you should see responses like those on in the picture on the right. If you see asterisks, that means that a router or server along the way didn't respond.
Note that when you traceroute to your ExaVault server, our firewalls may not send responses back.
If the last lines in the traceroute list asterisks instead of a server and response times,
don't worry about it. Use Ping to test connectivity to the server.
Copying and pasting from the Terminal is just like copying and pasting from any other application:
Notes:
% + C).% + V)

Using traceroute in Linux, BSD, and other Unices is really easy:
traceroute your-account.exavault.com
Note: on some systems, the command will be /usr/sbin/traceroute
After you've entered the command, you should see responses like those on in the picture on the right. If you see asterisks, that means that a router or server along the way didn't respond.
Note that when you traceroute to your ExaVault server, our firewalls may not send responses back.
If the last lines in the traceroute list asterisks instead of a server and response times,
don't worry about it. Use Ping to test connectivity to the server.
Copying and pasting from the Terminal is just like copying and pasting from any other application:
Notes:
CTRL + C).CTRL + V)
To understand why traceroute is useful, you'll need to have some basic knowledge of how
data transfers (particularly
FTP and SFTP) work:
You might think that is a terribly inefficient way to transfer data. However, the
send - acknowledgement /re-send method ensures that data will not be corrupted during transfer.
What that means to you is that FTP and SFTP are very safe and reliable ways to transfer data.
traceroute works in a similar way to data transfers:
Therefore, if you are experiencing slow transfer speeds, a traceroute can help point out
where the bottleneck is.
Here are the rules of thumb we use at ExaVault for traceroute response times:
To be pedantic, there is quite a lot more to FTP and SFTP transfers than what is listed here. In addition, the trivial file transfer protocol (TFTP) doesn't behave like this at all. Semantics aside, we wrote this article for the lay person who is trying to figure out why their file transfer is going slower than they anticipated.
In other words, we hope to give you some basic insight into the very technical and geeky details of file transfers. To that end, we have decided to leave out the some of the more sleepy details such as ICMP Echo Requests and Time to Live.