A ping and traceroute (also known as tracert) test can be used when troubleshooting possible connection issues to a website. The results of this test can be used to rule out a connection issue or, in the event of a connection issue, identify where in the network the issue is occurring.

If our Support Team has requested you run a ping and trace test, when you email the results, please be sure to include the IP you are connecting from in your email to Support. You can view and copy your IP address using our IP check tool here:

http://www.support.webhostinghub.com/ipcheck.php

In the examples below, we have done a ping and trace on example.com. Please replace example.com with your actual domain name.

Run Ping and Tracert in Windows

  1. Click your Start menu and select Programs > Accessories > Command Prompt
  2. In the command line window that opens, type ping example.com, and hit Enter.
  3. Once the test is complete, type tracert example.com and hit Enter.
  4. Please copy and paste the results from both tests and send them to This email address is being protected from spambots. You need JavaScript enabled to view it. so that we can look into your issue further.
  5. Type exit to close the command line window.

In order to copy the text in a Windows command line window, simply right-click with your mouse in the command line window. You can either choose MARK or SELECT ALL. If you select MARK, then you will need left-click and drag in order to select text in the command line window. Once the text is selected hold down your CTRL key and then hit the 'C' key in order to copy. You can then click on your email or text document and then use CTRL-V (hold down the CTRL key and then tap the 'V' key) to paste the text you have copied. The same procedure is used if you selected all of the text in the command line window.

Run Ping and Traceroute in Mac OS

  1. Open Applications and then open Utilities.
  2. Open Terminal.
  3. Type: ping example.com and hit Enter.
  4. Stop the ping after 4 or 5 results by holding down CTRL-C.
  5. When that is done, type traceroute example.com and hit Enter.
  6. Please copy and paste the results from both tests and send them to This email address is being protected from spambots. You need JavaScript enabled to view it. so that we can look into your issue further.
  7. Close Terminal.

In order to copy text in the Macintosh Terminal window, simply use your mouse or touchpad to highlight the text (click and drag over the text) then use hold down the command key and tap the letter 'C' to copy the text. Next, click in your email or text document and then hold down the command key and tap the letter 'V' to paste the text. You can select ALL of the text in the Terminal window by left-clicking in the Terminal window (to make it active) and then holding down the command key and tapping 'A'.

Did you find this article helpful?

We value your feedback!

Why was this article not helpful? (Check all that apply)
The article is too difficult or too technical to follow.
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
How did you find this article?
Please tell us how we can improve this article:
Email Address
Name

new! - Enter your name and email address above and we will post your feedback in the comments on this page!

Did you find this article helpful?

Comments

n/a Points
2014-05-06 11:41 am

ping

erchinfo@INC-0039:~$ ping incentivare.com.brPING incentivare.com.br (70.39.151.96) 56(84) bytes of data.64 bytes from mx1.incentivare.com.br (70.39.151.96): icmp_req=1 ttl=49 time=154 ms64 bytes from mx1.incentivare.com.br (70.39.151.96): icmp_req=2 ttl=49 time=158 ms64 bytes from mx1.incentivare.com.br (70.39.151.96): icmp_req=3 ttl=49 time=162 ms64 bytes from mx1.incentivare.com.br (70.39.151.96): icmp_req=4 ttl=49 time=151 ms

traceroute

erchinfo@INC-0039:~$ traceroute incentivare.com.brtraceroute to mx1.incentivare.com.br (70.39.151.96), 64 hops max 1   192.168.0.1 (192.168.0.1) 0.214ms 0.132ms 0.140ms  2   186.220.16.1 (186.220.16.1) 61.732ms 58.886ms 50.840ms  3   201.6.0.95 (201.6.0.95) 15.608ms 12.258ms 10.076ms  4   201.6.0.49 (201.6.0.49) 12.823ms 12.403ms 15.032ms  5   201.6.40.1 (201.6.40.1) 16.763ms 11.397ms 16.198ms  6   201.56.189.13 (201.56.189.13) 12.286ms 12.754ms 19.129ms  7   200.230.159.206 (200.230.159.206) 16.381ms 15.545ms 16.515ms  8   200.230.220.46 (200.230.220.46) 139.343ms 151.630ms 155.123ms  9   4.71.230.241 (4.71.230.241) 191.470ms 161.545ms 150.354ms  10   4.69.155.62 (4.69.155.62) 153.745ms 152.983ms 156.944ms  11   4.69.134.65 (4.69.134.65) 164.605ms 152.682ms 175.739ms  12   4.69.201.50 (4.69.201.50) 152.269ms 153.170ms 153.271ms  13   4.69.201.93 (4.69.201.93) 160.857ms 153.474ms 149.634ms  14   4.69.134.154 (4.69.134.154) 149.197ms 159.433ms 176.146ms  15   4.69.149.142 (4.69.149.142) 167.838ms 152.417ms 156.808ms  16   4.79.22.110 (4.79.22.110) 155.634ms 156.774ms 153.520ms  17   70.39.234.254 (70.39.234.254) 155.047ms 153.565ms 153.537ms  18   70.39.151.96 (70.39.151.96) 151.360ms 153.293ms 153.432ms

 

Staff
13,785 Points
2014-05-06 12:16 pm
Hello Eldrin,

In reviewing your traceroute report, you can see that the signal begins to slow down at around hop 9, which is in Sao Paulo, Brazil. It then maintains roughly the same speed as it goes through the New York line and finally to our datacenter on the East Coast.

While the numbers are not bad, anything over 100 is viewed as a little slow, the higher that number is, the slower the connection.

Kindest Regards,
Scott M
n/a Points
2014-06-30 12:44 pm

Ping

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

 

C:\Users\IROMINI ABIODUN>ping genteelconsultltd.com

 

Pinging genteelconsultltd.com [46.16.188.2] with 32 bytes of data:

Reply from 46.16.188.2: bytes=32 time=123ms TTL=49

Reply from 46.16.188.2: bytes=32 time=131ms TTL=49

Reply from 46.16.188.2: bytes=32 time=130ms TTL=49

Reply from 46.16.188.2: bytes=32 time=147ms TTL=49

 

Ping statistics for 46.16.188.2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 123ms, Maximum = 147ms, Average = 132ms

 

C:\Users\IROMINI ABIODUN>

Staff
10,104 Points
2014-06-30 1:08 pm
Hello Femi,

Thank you for your question. Your Ping looks fine, and everything seems to be responding reasonably fast.

Was there any issues with your trace route?

I also navigated to the site listed and it is working for me at this time. What issues are you experiencing?

If you have any further questions, feel free to post them below.
Thank you,

-John-Paul
n/a Points
2014-09-11 3:03 pm

Last login: Thu Sep 11 13:54:28 on ttys000

silvia-imac-5:~ iahsa$ ping humblewildcatfootball.com

PING humblewildcatfootball.com (208.109.181.52): 56 data bytes

64 bytes from 208.109.181.52: icmp_seq=0 ttl=55 time=70.974 ms

64 bytes from 208.109.181.52: icmp_seq=1 ttl=55 time=71.299 ms

64 bytes from 208.109.181.52: icmp_seq=2 ttl=55 time=71.788 ms

64 bytes from 208.109.181.52: icmp_seq=3 ttl=55 time=71.666 ms

64 bytes from 208.109.181.52: icmp_seq=4 ttl=55 time=70.676 ms

^C

--- humblewildcatfootball.com ping statistics ---

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 70.676/71.281/71.788/0.416 ms

silvia-imac-5:~ iahsa$ traceroute humblewildcatfootball.com

traceroute to humblewildcatfootball.com (208.109.181.52), 64 hops max, 52 byte packets

 1  modem (192.168.0.1)  2.133 ms  1.724 ms  1.984 ms

 2  tx-184-7-112-1.dhcp.embarqhsd.net (184.7.112.1)  17.678 ms  17.890 ms  17.689 ms

 3  67.239.78.29 (67.239.78.29)  17.924 ms  17.766 ms  17.840 ms

 4  206.51.81.38 (206.51.81.38)  28.868 ms  29.454 ms  29.240 ms

 5  bb-dllstx37-jx9-02-ae0.core.centurytel.net (206.51.69.58)  28.726 ms  28.514 ms  28.060 ms

 6  bb-lsvgnvxb-jx9-02-xe-1-1-0.core.centurytel.net (206.51.69.154)  62.088 ms  62.481 ms  62.091 ms

 7  * * *

 

 8  * * *

Staff
2,342 Points
2014-09-11 3:45 pm
From the trace that you provided, it looks like the connection is timing out within your ISP. I recommend contacting them for more information. Unfortunately, as it does not reach our network at all, I am unable to provide any additional information.
n/a Points
2015-01-05 5:17 pm

PING example.com (93.184.216.34): 56 data bytes

64 bytes from 93.184.216.34: icmp_seq=0 ttl=52 time=181.586 ms

64 bytes from 93.184.216.34: icmp_seq=1 ttl=52 time=178.383 ms

64 bytes from 93.184.216.34: icmp_seq=2 ttl=52 time=177.242 ms

64 bytes from 93.184.216.34: icmp_seq=3 ttl=52 time=180.060 ms

 

 

 

traceroute to example.com (93.184.216.34), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  4.443 ms  0.758 ms  0.735 ms

 2  62.52.200.154 (62.52.200.154)  34.217 ms  67.228 ms  34.117 ms

 3  ge-7-1-2-0.01.xd.0176-03.ham.de.net.telefonica.de (62.53.7.242)  61.721 ms  33.753 ms  29.805 ms

 4  ae0-0.0001.prrx.02.ham.de.net.telefonica.de (62.53.7.217)  31.821 ms  34.345 ms  32.959 ms

 5  ae0-0-grtdusix1.red.telefonica-wholesale.net (84.16.7.233)  36.087 ms  39.078 ms  47.074 ms

 6  te-0-1-0-13-grtlontlw1.red.telefonica-wholesale.net (94.142.120.242)  63.152 ms

    xe6-0-2-0-grtloneq1.red.telefonica-wholesale.net (94.142.119.90)  59.633 ms  65.418 ms

 7  xe5-0-2-0-grtnycpt2.red.telefonica-wholesale.net (94.142.116.249)  199.759 ms *

    xe3-1-8-0-grtnycpt3.red.telefonica-wholesale.net (213.140.37.249)  136.356 ms

 8  xe4-1-7-0-grtmiana2.red.telefonica-wholesale.net (94.142.123.141)  180.543 ms

    xe1-1-6-0-grtmiana2.red.telefonica-wholesale.net (5.53.6.198)  175.823 ms

    xe-0-1-5-grtmiana2.red.telefonica-wholesale.net (94.142.124.161)  184.440 ms

 9  xe7-1-8-grtmiana2.red.telefonica-wholesale.net (94.142.125.225)  184.752 ms

    edgecast-xe-0-0-10-grtmiana2 (176.52.252.202)  177.089 ms

    xe7-1-8-grtmiana2.red.telefonica-wholesale.net (94.142.125.225)  189.795 ms

10  213.140.55.82 (213.140.55.82)  173.109 ms

    192.16.6.93 (192.16.6.93)  169.286 ms  170.720 ms

11  93.184.216.34 (93.184.216.34)  179.862 ms  175.564 ms  174.145 ms

Staff
13,785 Points
2015-01-05 5:41 pm
Hello tmd,

I took a look at your traceroute and see that the hop that begins to have some latency is number 7, IP: 94.142.116.249. This IP appears to be in or around New York City. The rest of the hops do not increase the time, so it appears there may simply be some priority shifting in packets at more heavily trafficked routers along the way to your web server. Please let us know if you have any further questions.

Kindest Regards,
Scott M

Post a Comment

Name:
Email Address:
Phone Number:
Comment:
Submit

Please note: Your name and comment will be displayed, but we will not show your email address.

Related Questions

Here are a few questions related to this article that our customers have asked:
Would you like to ask a question about this page? If so, click the button below!

Help Center Search

Current Customers

Email: support@WebHostingHub.com Ticket: Submit a Support Ticket
Call: 877-595-4HUB (4482)
757-416-6627 (Intl.)
Chat: Click To Chat Now

Ask the Community

Get help with your questions from our community of like-minded hosting users and Web Hosting Hub Staff.

Not a Customer?

Get web hosting from a company that is here to help.