To run a ping test in Windows 7:

  1. Click Start menu
  2. Type cmd in the white box and press enter to open the command prompt
  3. Type ping <servername> and hit Enter (e.g ping login2.blackbaudhosting.com)

To run a ping test in Windows XP:
  1. Click Start menu
  2. Click Run
  3. Type cmd and press enter to open the command prompt
  4. Type ping <servername> and hit Enter (e.g ping login2.blackbaudhosting.com

To run a ping test on a Mac:
  1. Open Network Utility (located inside Applications > Utilities)
  2. Select Ping
  3. Fill out the “Enter the network that you want to ping” field. Here you can enter the IP address or web URL.
  4. Click Ping

Ping the appropriate URL depending on which datacenter the customer is on:

Boston Datacenter: ping login2.blackbaudhosting.com
EU (Amsterdam) Datacenter: ping login01.blackbaud.net
Orange County Datacenter: ping login1.blackbaudhosting.com
Vancouver Datacenter: ping appsca.blackbaudondemand.com


The results will appear as below:

Pinging login2.blackbaudhosting.com [63.128.14.233] with 32 bytes of data:
Reply from 63.128.14.233: bytes=32 time=39ms TTL=240
Reply from 63.128.14.233: bytes=32 time=38ms TTL=240
Reply from 63.128.14.233: bytes=32 time=40ms TTL=240
Reply from 63.128.14.233: bytes=32 time=38ms TTL=240

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


Now that we have the results, we need to understand what these results mean.

Reply from offers you the IP address that the server resolves to
bytes= is the size of the packet which you sent to the server
time= the number of ms the server took to reply to you
TTL= Time to Live of the packet

The most important information in the ping test is the time= field.  We want this response time to be less than 150ms, and for optimum performance less than 75ms.

There are also switches available for the ping command which can prove further useful when trying to diagnose performance issues in the hosted environment.  Please find a list of switches below:

-t  by adding -t into your ping, this will ping continuously until the user presses crtl+c to force the ping to stop
-f by adding -f into your ping, you are forcing the server to not fragment the packets for a response time improvement.  
-l by adding -l into the ping, you can specify the size of the packet you want to send the server
>C:\filename.txt By adding this to the end of the ping command, you can specify the output to a text file on the local hard drive instead of in the command prompt window

Example pings:
ping -t -l1000 -f login2.blackbaudhosting.com
This ping is a command to continuously ping the server with 1000byte packets which are non-fragmented. 

Pinging login2.blackbaudhosting.com [63.128.14.233] with 0 bytes of data:
Reply from 63.128.14.233: bytes=0 time=38ms TTL=240
Reply from 63.128.14.233: bytes=0 time=39ms TTL=240
Reply from 63.128.14.233: bytes=0 time=42ms TTL=240
Reply from 63.128.14.233: bytes=0 time=56ms TTL=240
Reply from 63.128.14.233: bytes=0 time=40ms TTL=240
Reply from 63.128.14.233: bytes=0 time=54ms TTL=240
Reply from 63.128.14.233: bytes=0 time=68ms TTL=240
Reply from 63.128.14.233: bytes=0 time=47ms TTL=240
Reply from 63.128.14.233: bytes=0 time=42ms TTL=240
Reply from 63.128.14.233: bytes=0 time=37ms TTL=240
Reply from 63.128.14.233: bytes=0 time=37ms TTL=240

Ping statistics for 63.128.14.233:
    Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 37ms, Maximum = 68ms, Average = 45ms