To run a traceroute in Windows 7:
  1. Click Start menu
  2. Type cmd in the white box and press enter to open the command prompt
  3. Type tracert [URL of the appropriate datacenter, as listed below]
  4. Hit Enter

To run a traceroute in Windows XP:
  1. Click Start menu
  2. Click Run
  3. Type cmd in the white box and press enter to open the command prompt
  4. Type tracert [URL of the appropriate datacenter, as listed below] 
  5. Hit Enter 

To run a traceroute in Windows 10:
  1. Right-click Start menu(You can also bring up the Run window by pressing "Windows / r" on your keyboard.)
  2. Click Run
  3. Type cmd in the white box and press enter to open the command prompt
  4. Type tracert [URL of the appropriate datacenter, as listed below] 
  5. Hit Enter 

Trace to the appropriate URL depending on which datacenter the customer is on:
  • Boston Datacenter: tracert ctx-login2.blackbaudhosting.com also run tracert testlogin2.blackbaudhosting.com
  • EU (Amsterdam) Datacenter: tracert login01.blackbaud.net
  • Orange County Datacenter: tracert login1.blackbaudhosting.com
  • Vancouver Datacenter: tracert appsca.blackbaudondemand.com

The results will appear as below:
 
Boston Datacenter: tracert ctx-login2.blackbaudhosting.com

Tracing route to ctc-login2.blackbaudhosting.com [63.128.14.233] over a maximum of 30 hops:
  1. 3 ms 2 ms 4 ms 10.31.0.5
  2. 2 ms 1 ms <1 ms 10.0.0.13
  3. 2 ms 1 ms 1 ms 216.235.192.4
  4. 18 ms 13 ms 17 ms 12.86.96.149
  5. 15 ms 14 ms 20 ms cr83.attga.ip.att.net [12.122.141.62]
  6. 14 ms 16 ms 22 ms cr1.attga.ip.att.net [12.123.22.109]
  7. 18 ms 10 ms 11 ms attga03jt.ip.att.net [12.122.84.21]
  8. 12 ms 11 ms 12 ms 208.173.60.237
  9. 13 ms 10 ms 11 ms cr2-te-0-0-0-0.atlanta.savvis.net [204.70.200.2]
  10. 31 ms 33 ms 34 ms cr2-pos-0-0-0-0.NewYork.savvis.net [204.70.192.2]
  11. 38 ms 32 ms 34 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
  12. * 42 ms 39 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198.174]
  13. 37 ms 37 ms 37 ms hr1-bo3-te-1-0-0.Waltham3bo3.savvis.net [204.70.202.14]
  14. 40 ms 37 ms 37 ms das1-v3005.bo3.savvis.net [205.139.96.50]
  15. 38 ms 37 ms 39 ms 63.128.14.233
Trace complete.

Now that we have the results, we need to understand what these results mean.
  • The first column is a representation of the "hop" number, or what step the traffic has taken to reach that IP address.
  • The next three columns represent the time that the traffic took to reach that hop, on three separate attempts, in milliseconds.
  • The last column is the hostname of the hop, and its associated IP address.
The most important information in the tracert tests are the three time fields:
  • A perfect trace should have less than 16 hops, each hop less than 75ms and no asterisks.
  • An acceptable trace should have less than 23 hops, each hop less than 200ms and 1 to 4 asterisks.
  • A bad trace will have 20 to 30 hops, 200ms+ and/or 25% asterisks and many "request timed out".
  • Each of these raise concern that data may not be transmitting properly through the internet, as an asterisk/star in the place of a response time means that the server did not respond.