In this tutorial:

A number of factors contribute to how fast your connection to our servers is, including:

  • Your computer health
  • The connection you have to your ISP (internet service provider)
  • The number of network hops between your ISP and our servers
  • The amount of traffic our servers are currently having

Running a ping test can help you determine if your website is slow because of a connection issue. If it is, then running a traceroute test can help you to determine where in the connection there is a slow down.

If you're on Windows you might also find it handy to use PingPlotter to help troubleshoot network slowdowns.

How to Run a Ping / Traceroute Test

In the examples below, you will be asked to ping and traceroute yourdomain.com. Please replace yourdomain.com with your actual domain name.

BETA! - We are currently developing a tool to automatically and consistently analyze the results of a traceroute test. If you run the traceroute test as described below, you can use our traceroute parser tool here to see if you may be experiencing a connectivity problem.

Windows

If you are on a Windows computer:

  1. Click your start menu and choose run
  2. Type cmd and click OK
  3. Type: ping yourdomain.com and hit enter
  4. When it is done, type tracert yourdomain.com and hit enter.

When both tests are complete, you will want to copy and paste the results in an email and send them to support@inmotionhosting.com for further review.. To copy the results, right click in the command prompt and choose Select all. When everything is highlighted, hit Enter to copy the results to the clipboard so that you can paste them into an email message. Be sure to include your current IP address. If you are unsure of your current IP address please visit the link below to obtain it:
What is my current IP Address?

Mac

If you are on a Mac:

  1. Open Applications and then open Utilities.
  2. Open Terminal.
  3. Type: ping yourdomain.com and hit enter. Stop the ping after 4 or 5 results by holding down CTRL-C.
  4. When that is done, type: traceroute yourdomain.com and then hit enter.

iPad

If you're using an iPad, it doesn't appear that iPads have ping / traceroute functionality. There are apps that can help, such as this one. If you have helpful information about how to ping / tracert from an ipad, let us know!

After you have run the tests...

When both tests are complete, you will want to copy and paste the results in an email and send them to support@inmotionhosting.com. Be sure to include your current IP address. If you are unsure of your current IP address please visit the link below to obtain it:
What is my current IP Address?

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!

Related Questions

Here are a few questions related to this article that our customers have asked:
Cannot access mail using a specific ISP
Why Is My Drupal Site Loading Slowly?
Would you like to ask a question about this page? If so, click the button below!
Ask a Question
n/a Points
2014-03-15 6:51 pm

Daniels-MacBook-Pro:Downloads daniel$ ping www.caldoefreddo.com.br

PING caldoefreddo.com.br (198.46.91.103): 56 data bytes

64 bytes from 198.46.91.103: icmp_seq=0 ttl=49 time=155.368 ms

64 bytes from 198.46.91.103: icmp_seq=1 ttl=49 time=152.603 ms

64 bytes from 198.46.91.103: icmp_seq=2 ttl=49 time=155.028 ms

64 bytes from 198.46.91.103: icmp_seq=3 ttl=49 time=156.175 ms

64 bytes from 198.46.91.103: icmp_seq=4 ttl=49 time=159.636 ms

64 bytes from 198.46.91.103: icmp_seq=5 ttl=49 time=154.655 ms

64 bytes from 198.46.91.103: icmp_seq=6 ttl=49 time=155.838 ms

64 bytes from 198.46.91.103: icmp_seq=7 ttl=49 time=157.493 ms

64 bytes from 198.46.91.103: icmp_seq=8 ttl=49 time=154.178 ms

^C

--- caldoefreddo.com.br ping statistics ---

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

round-trip min/avg/max/stddev = 152.603/155.664/159.636/1.900 ms

Daniels-MacBook-Pro:Downloads daniel$ traceroute www.caldoefreddo.com.br

traceroute to caldoefreddo.com.br (198.46.91.103), 64 hops max, 52 byte packets

 1  192.168.0.2 (192.168.0.2)  5.112 ms  2.278 ms  0.863 ms

 2  badc1801.virtua.com.br (186.220.24.1)  28.613 ms  28.872 ms  30.086 ms

 3  spojabrtd01.virtua.com.br (201.6.0.95)  10.085 ms  12.785 ms  9.452 ms

 4  c9062801.virtua.com.br (201.6.40.1)  16.380 ms  17.936 ms  10.763 ms

 5  embratel-t0-1-0-2-uacc01.spo.embratel.net.br (201.56.239.13)  12.888 ms

    embratel-t0-0-0-1-uacc01.spoph.embratel.net.br (200.245.154.13)  15.647 ms

    embratel-t0-3-2-0-tacc01.spoph.embratel.net.br (200.178.127.21)  14.443 ms

 6  ebt-t0-2-0-11-tcore01.spo.embratel.net.br (200.230.158.86)  126.416 ms

    ebt-t0-5-0-2-tcore01.spo.embratel.net.br (200.230.159.158)  19.147 ms

    ebt-t0-2-0-11-tcore01.spo.embratel.net.br (200.230.158.86)  138.964 ms

 7  ebt-p0-0-2-0-intl01.nyk.embratel.net.br (200.230.251.62)  139.727 ms

    ebt-bp1111-intl01.nyk.embratel.net.br (200.230.220.46)  134.616 ms  137.180 ms

 8  ae59.edge2.newyork1.level3.net (4.71.230.241)  140.106 ms  152.869 ms  146.748 ms

 9  vlan70.csw2.newyork1.level3.net (4.69.155.126)  140.074 ms

    vlan80.csw3.newyork1.level3.net (4.69.155.190)  143.754 ms  151.734 ms

10  ae-91-91.ebr1.newyork1.level3.net (4.69.134.77)  153.669 ms  151.616 ms

    ae-71-71.ebr1.newyork1.level3.net (4.69.134.69)  156.258 ms

11  ae-57-57.ebr2.washington12.level3.net (4.69.201.66)  153.660 ms

    ae-58-58.ebr2.washington12.level3.net (4.69.201.70)  142.819 ms

    ae-57-57.ebr2.washington12.level3.net (4.69.201.66)  147.360 ms

12  ae-37-37.ebr2.washington1.level3.net (4.69.132.89)  150.455 ms

    ae-45-45.ebr2.washington1.level3.net (4.69.143.221)  140.181 ms

    ae-37-37.ebr2.washington1.level3.net (4.69.132.89)  147.769 ms

13  ae-82-82.csw3.washington1.level3.net (4.69.134.154)  144.265 ms  140.164 ms  149.789 ms

14  ae-1-60.edge2.washington1.level3.net (4.69.149.14)  149.509 ms

    ae-2-70.edge2.washington1.level3.net (4.69.149.78)  151.211 ms

    ae-4-90.edge2.washington1.level3.net (4.69.149.206)  141.729 ms

15  inmotion-ho.edge2.washington1.level3.net (4.79.22.110)  152.606 ms  157.045 ms  153.142 ms

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

 

24  * *^C

 

Staff
9,384 Points
2014-03-17 8:58 am
It appears that you are having a bit of latency from the beginning, but completely time out at the datacenter. I recommend contacting technical support with this information as your IP may be blocked.
n/a Points
2014-03-21 10:37 am

Microsoft Windows [Version 6.1.7601]

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

 

C:\Users\user>ping yourdomain.com

 

Pinging yourdomain.com [74.208.239.241] with 32 bytes of data:

Reply from 74.208.239.241: bytes=32 time=362ms TTL=52

Reply from 74.208.239.241: bytes=32 time=259ms TTL=52

Reply from 74.208.239.241: bytes=32 time=303ms TTL=52

Reply from 74.208.239.241: bytes=32 time=287ms TTL=52

 

Ping statistics for 74.208.239.241:

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

Approximate round trip times in milli-seconds:

    Minimum = 259ms, Maximum = 362ms, Average = 302ms

 

C:\Users\user>tracert yourdomain.com

 

Tracing route to yourdomain.com [74.208.239.241]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2    94 ms    72 ms    74 ms  119.95.224.1

  3   252 ms   147 ms   163 ms  119.93.255.221

  4   237 ms   177 ms   160 ms  210.213.130.118

  5   251 ms   248 ms   235 ms

Staff
9,384 Points
2014-03-21 10:45 am
It looks like you did not replace yourdomain.com with your actual domain. In addition to this, I see that you have a large amount of latency within your network that you may want to investigate.
n/a Points
2014-03-21 10:50 am

eh.. sorry, I really don't have any idea with troubleshooting in regards of my ip or whatever. It's just that for 3 straight days I don't have any internet connection and now that I do, it's so slow, and it's very erractic. Any Ideas? Badly needed help. Thanks.

Staff
10,207 Points
2014-03-21 11:22 am
Hello kat,

When you perform the Ping/Tracert, replace the words "yourdomain.com" with your real web address. For example if your website is examplewebsite.com you would enter:

ping examplewebsite.com
&
tracert examplewebsite.com

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

-John-Paul
n/a Points
2014-03-24 2:32 am

ping triumphlink.com

PING triumphlink.com (205.178.152.6): 32 data bytes

Reply from 205.178.152.6: bytes=32 tme314ms TTL=112

Reply from 205.178.152.6: bytes=32 tme342ms TTL=112

Reply from 205.178.152.6: bytes=32 tme330ms TTL=112

Reply from 205.178.152.6: bytes=32 tme339ms TTL=112

Ping statistics for 205.178.152.6:

packets: Sent = 4, Received = 4, Lost = 0 <0% loss),

Approximate round trip times in milli-seconds:

Minimun = 314ms, Maximun = 342ms, Average = 331ms

 

tracert triumphlink.com

Tracing route to triumphlink.com [205.178.152.6]

1     2ms     2ms     1ms  180.168.59.173

2     2ms     2ms     1ms  124.74.50.145

3     3ms     6ms     7ms  124.74.209.205

4     5ms     6ms     6ms  61.152.86.198

5     **        **       **     Time Out

6     3ms     3ms     3ms  202.97.35.94

7   261ms   262ms  259ms  202.97.58.182

8   362ms   362ms  360ms   202.97.49.110

9      **       364ms    **  1ax2-pr2-se-10-0-0-0.us.twtelcom.net [64.132.69.109]

10   445ms  447ms    **  atl1-ar3-ge-0-1-0-0.us.twtelcom.net [66.192.243.106]

11   409ms  410ms    **  66-193-226-118.static.twtelcom.net [66.193.226.118]

12      **     316ms    317ms  209.17.112.38

13      **     413ms    413ms  w2k3-web6.prod.netsolhost.com [205.178.152.6]

14    413ms  413ms    **       w2k3-web6.prod.netsolhost.com [205.178.152.6]

13    311ms  312ms   313ms  w2k3-web6.prod.netsolhost.com [205.178.152.6]

 

Staff
10,207 Points
2014-03-24 10:21 am
Hello Ken,

I am seeing a lot of latency starting on the 5th hop; which can cause connection issues. The latency continues to the 14th hop which is on Network Solutions.

I recommend contacting your ISP regarding your connection problems, and providing this traceroute as evidence.

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

-John-Paul
Staff
17,716 Points
2014-04-01 5:25 pm
Hello Page,

Sorry to hear about your problem. Our service is really for InMotion customers, and you should be sending an email into the Technical Support team. All information posted on this page is open to the public. If you're unable to reach a particular host, then we can generally backtrack through the tracert to see where the communication is breaking up. Tracert information is basically providing connection information coming from your location going to a particular location. In this case, it's showing how you're connecting TO nyspi.org. This information may be valuable to either the hosting service you're trying to reach or the internet service provider you're using make to the connection. When I try to tracert from here to the same location, it also dies at the same IP. You should contact the host you're trying to connect to and have them investigate it from their end. Or you may want to try asking your ISP for further assistance to see if they can find a cause.

Regards,
Arnel C.
n/a Points
2014-04-02 1:08 pm

Ah, Thought that ws mighty generous of you. I appreciate your response and sorry I am where I don't belong. I found you tracert description helpful in any event. Thanks!

Staff
20,113 Points
2014-04-02 1:11 pm
Hello Page,

We are happy we were able to help you in any case. We do not mind helping non-customers, but sometimes we cannot assist as much as we would like due to the fact we cannot see specific information. In any case, you are always welcome to ask questions in our support center.

Kindest Regards,
Scott M
n/a Points
2014-11-13 4:39 pm

hello, i really need your help: Its about Ping and Traceroute:

Here are the questions:

Explain what conclusions you can draw when it comes to the last two quotas and why to take double the distance? Why increases / decreases the average speed of the signal when you send it away?

Why are the distances longer / shorter between the servers when you send the signal farther?

 

Hope to hear from you soon. Thank you very much.

Staff
17,716 Points
2014-11-13 4:54 pm
Hello Jenny,

Thanks for your question. We can't really make any judgements on your traceroute without a sample of it. If you can provide it, then we can see what's happening. If you want to learn how to understand and read a traceroute, then please see: Reading a Traceroute. A signal speed doesn't really increase. The overall time does decrease as the distance increases. When you're looking at the times of the hops, some of them may be SHORTER in distance than the others, hence the shorter time. There are other factors, but for the purposes of your understanding, just remember that the signal is travelling across fiber and wire in order to get one from location to another. The hops you're seeing are the junctions through which the signal is traveling (in hops) to get to its destination.

I hope that helps to clarify the issue for you. If you have any further questions or comments, please let us know.

Regards,
Arnel C.
n/a Points
2014-11-13 5:12 pm

  Australia Cypress Denmark Indonesia Switzerland distance from Sweden     30     km distance from Sweden x2     60     km time the packets traveled (RTT)     100.3     ms number of hops     13   13   2 x distance/RTT = v     0.6     million m/s distance/number of hops   #DIV/0! 2.3 #DIV/0! 0.0 km/hop               ping value     100       ping value     101       ping value     100       ping value     100       ping value            

 

C:> tracert trace.tele.dk

Tracing route to noc.tele.dk [193.162.154.26] over a maximum of 30 hops:

   1 1094 ms 2 ms 2 ms 192.168.0.1

   2:04 a.m. ms 4 ms 5 ms gw1.A218.cust.bahnhof.se [85.24.240.1]

   3:04 a.m. ms 5 ms 4 ms hsb-A218.c3750-stortorget.bahnhof.net [85.24.152.50]

   4:04 a.m. ms 4 ms 4 ms stortorget-mmo.c7600-limhamn.bahnhof.net [85.24.151.29]

   5 1215 ms 5 ms 4 ms 82.96.55.41

   6:05 a.m. ms 4 ms 5 ms v1306.svv-cr1-r72.cph.dk.p80.net [82.96.1.26]

   7:05 a.m. ms 5 ms 6 ms ge-0-1-0.1000M.virnxj7.ip.tele.dk [192.38.7.39]

   8:07 a.m. ms 6 ms 6 ms pos0-0.622M.virnxg5.ip.tele.dk [83.88.13.18]

   9 1165 ms 9 ms 9 ms pos0-1-0-0.2488M.boanqh2.ip.tele.dk [83.88.20.229]

  10:10 a.m. ms 10 ms 10 ms pos0-0-0-0.9953M.arcnqh2.ip.tele.dk [83.88.26.30]

  11,158 ms 9 ms 9 ms pos1-0.2488M.arcnxg4.ip.tele.dk [83.88.13.82]

  24:09 ms 8 ms 9 ms so-1-2-0.622M.sltnxj2.ip.tele.dk [83.88.29.134]

  13:09 ms 8 ms 8 ms noc.tele.dk [193.162.154.26]

Trace complete.

 

That is the sample: of the questions i asked before: sorry i dont know how to attached a file here:  

Explain what conclusions you can draw when it comes to the last two quotas and why to take double the distance?

           
Staff
10,207 Points
2014-11-13 6:21 pm
Hello Karen,

The internet is similar to a highway, in that there are many paths/highways it can take from your computer to the server. The best route to take is determined by your ISP or Internet service provider: such as TimeWarner, Comcast, etc.

When you perform a traceroute, it pings the IP of each device along the way twice. This is why you see two times listed, such as 8ms, or 9ms. This stands for 8 milliseconds, and 9 milliseconds, and it is how long it takes for that specific device to respond.

So on your traceroute, the last 2 hops are responding within 8 milliseconds average, which is pretty quick.

Are you having problems resolving to your site?

Thank you,
John-Paul
n/a Points
2014-06-25 6:34 pm

My WebSite is very slow.

Here is trace route result

  1     8 ms    10 ms     1 ms  192.168.1.1

  2    40 ms    25 ms    46 ms  10.32.249.1

  3    27 ms    30 ms    30 ms  G1-1-0-5.NYCMNY-LCR-21.verizon-gni.net [130.81.196.124]

  4    90 ms    25 ms    34 ms  ae3-0.NY325-BB-RTR1.verizon-gni.net [130.81.199.162]

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8   118 ms   112 ms   111 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]

  9   112 ms   112 ms   118 ms  ae-38-38.ebr2.Washington1.Level3.net [4.69.201.85]

 10   142 ms   118 ms   112 ms  ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]

 11   121 ms   119 ms   111 ms  ae-91-91.ebr1.Washington1.Level3.net [4.69.134.141]

 12   123 ms   141 ms   110 ms  ae-4-4.ebr3.LosAngeles1.Level3.net [4.69.132.81]

 13   117 ms   123 ms   139 ms  ae-73-73.csw2.LosAngeles1.Level3.net [4.69.137.38]

 14   178 ms   165 ms   111 ms  ae-2-70.edge3.LosAngeles1.Level3.net [4.69.144.73]

 15   104 ms    98 ms   114 ms  cr1.lax1.us.packetexchange.net [4.71.136.2]

 16     *        *        *     Request timed out.

 17    97 ms    99 ms    97 ms  biz136.inmotionhosting.com [173.247.246.8]

Here is Ping result

Reply from 173.247.246.8: bytes=32 time=91ms TTL=53

Reply from 173.247.246.8: bytes=32 time=91ms TTL=53

Reply from 173.247.246.8: bytes=32 time=91ms TTL=53

Reply from 173.247.246.8: bytes=32 time=92ms TTL=53

 

Ping statistics for 173.247.246.8:

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

Approximate round trip times in milli-seconds:

    Minimum = 91ms, Maximum = 92ms, Average = 91ms

 

Trace complete.

Staff
9,968 Points
2014-06-25 7:16 pm
Hello Rabbani,

It doesn't look like the main thing slowing your site down is the connection you have to the server. You are averaging a 91ms latency to the server which isn't too bad. Some of your visitors might have higher latency then yourself, and you would probably benefit by following a lot of the advice in a GTMetrix scan of your website for performance.

It looks like you are loading quite a bit of content on your main page with 138 requests and 2.6 MB worth of data. So even with a relatively fast connection it could make your website seem sluggish.

I would look at reducing the amount of external JavaScript you're including as well as optimizing your images a bit more. For instance you have the /images/iacf2.jpg image as one of the background images for your slider. This image is 229KB in size, and it looks like if you set the JPEG compression to around 50% it still looks just about the same at only a size of 35KB.

I would also look and enabling gzip compression so that your JavaScript and CSS files that are larger can be reduced in size. For instance your jquery-ui.min.js script could possibly save almost 145KB in size if gzip compressed before being sent to the web-browser.

You are also loading jQuery, Bootstrap, and it looks like a bunch of Google API components. I would recommend if possible loading up your site in Google Chrome and then pressing F12 to go into Developer mode and click on the Network tab, then hit Ctrl-F5 to do a forced refresh of your site letting Chrome record the time it takes to load the site. You can then click twice on the Size / Content heading to see the largest files being loaded.

- Jacob
n/a Points
2014-06-30 1:32 am

I hav ea problem with my client www.vadehra.com they have 4 MBPS Broadband Connection but their domain based mails are downloading very slow lik e2m attachment mail takes around 2~4 hours. otherwise browsing is fine. i tested on my pc my gmail mails ar eworking fine.

what test can i perform to spot the problem.

Staff
9,384 Points
2014-06-30 9:11 am
Try running a pin/trace to the mail server and determine if you are getting any latency or timeouts. Depending on the server's location and other variables, you may have issues with that specific location. I see that you are not hosted with us so I would not have exact information, but I recommend contacting the hosting provider for more information if the ping/trace comes out fine.
n/a Points
2014-07-10 6:18 am

C:\Users\admin>ping inmotionhosting.comPinging inmotionhosting.com [192.145.237.216] with 32 bytes of data:Reply from 192.145.237.216: bytes=32 time=194ms TTL=55Reply from 192.145.237.216: bytes=32 time=195ms TTL=55Reply from 192.145.237.216: bytes=32 time=194ms TTL=55Reply from 192.145.237.216: bytes=32 time=204ms TTL=55Ping statistics for 192.145.237.216:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 194ms, Maximum = 204ms, Average = 196msC:\Users\admin>tracert www.inmotionhosting.comTracing route to www.inmotionhosting.com [192.145.237.216]over a maximum of 30 hops:  1    10 ms    34 ms    15 ms  cm1.kappa80.maxonline.com.sg [58.182.80.1]  2    21 ms     8 ms    31 ms  172.20.24.65  3    16 ms     9 ms     *     172.20.24.65  4    16 ms    13 ms    21 ms  172.20.7.6  5    14 ms    14 ms    17 ms  203.117.35.45  6    20 ms    12 ms    14 ms  six2asr9kts01.starhub.net.sg [203.117.34.9]  7    13 ms    16 ms    19 ms  203.117.34.198  8    31 ms    32 ms    14 ms  six2-ultl-int01.starhub.net.sg [203.117.34.58]  9     *        *        *     Request timed out. 10   197 ms   194 ms   196 ms  corporate-colocation-inc.gigabitethernet2-19.core1.lax2.he.net [184.105.140.162] 11   241 ms   242 ms   199 ms  205.134.225.38 12   193 ms   198 ms   231 ms  vpimh6.inmotionhosting.com [173.247.246.116] 13   206 ms   222 ms   194 ms  www.inmotionhosting.com [192.145.237.216]Trace complete.C:\Users\admin>

Staff
9,384 Points
2014-07-10 9:58 am
It looks like you are getting some latency within your ISP. I recommend contacting them for further information.
n/a Points
2014-07-12 10:22 am

Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation.  All rights reserved.C:\Users\maku>tracert yourdomain.comTracing route to yourdomain.com [74.208.239.241]over a maximum of 30 hops:  1     *        *        *     Request timed out.  2     *        *        *     Request timed out.  3    17 ms    16 ms    16 ms  203.87.193.1  4    12 ms    27 ms    21 ms  121.54.3.253  5    58 ms    48 ms    64 ms  203.87.160.225  6   102 ms   294 ms    48 ms  203.87.160.110  7    37 ms    41 ms    41 ms  203.111.226.41  8    40 ms    45 ms    42 ms  210.213.244.217.static.pldt.net [210.213.244.217]  9   135 ms    58 ms    64 ms  210.213.131.62.static.pldt.net [210.213.131.62] 10    40 ms    47 ms    57 ms  210.213.133.57.static.pldt.net [210.213.133.57] 11   197 ms   174 ms   163 ms  sea-b1-link.telia.net [80.239.132.109] 12     *      249 ms   222 ms  chi-bb1-link.telia.net [62.115.137.90] 13   242 ms   238 ms   262 ms  kanc-b1-link.telia.net [62.115.139.21] 14   245 ms   239 ms   243 ms  1o1internet-ic-147344-kanc-b1.c.telia.net [80.239.196.110] 15   231 ms   239 ms   231 ms  ae-2.gw-dista-a.ga.mkc.us.oneandone.net [74.208.6.195] 16   236 ms   237 ms   236 ms  vl-982.gw-ps5.ga.mkc.us.oneandone.net [74.208.6.130] 17   233 ms   238 ms   236 ms  perfora.net [74.208.239.241]Trace complete.C:\Users\maku>

Staff
20,113 Points
2014-07-13 2:21 pm
Hello Markysugino,

There does not appear to be an issue with your connection to your server. I can see a little increase from hops 10 to 11, but that is where the signal leaves Manila and arrives in Washington state. The time shown is normal for a signal crossing the Pacific. We have an article on reading a ping and traceroute that can help you understand what is going on as well. If you are seeing sluggishness on your site, you will want to contact your ISP, which appears to be 1&1 from the traceroute information.

Kindest Regards,
Scott M
2014-08-25 2:44 pm
I am having a persistent synchronisation error on Outlook 2010. I have done the IMAP folder subscription, but the errors still persistent when I synchronise the folders.

I wrote to support, and they recommend that I do ping and tracert. This is my result:

ping donkangroup.com.ng

Pinging donkangroup.com.ng [198.46.81.164] with 32 bytes of data:
Reply from 198.46.81.164: bytes=32 time=201ms TTL=52
Reply from 198.46.81.164: bytes=32 time=199ms TTL=52
Reply from 198.46.81.164: bytes=32 time=310ms TTL=52
Reply from 198.46.81.164: bytes=32 time=226ms TTL=52

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

tracert donkangroup.com.ng

Tracing route to donkangroup.com.ng [198.46.81.164]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms homerouter.cpe [192.168.1.1]
2 * * * Request timed out.
3 43 ms * 47 ms 10.200.15.1
4 44 ms 37 ms 38 ms 41.221.166.33
5 35 ms 39 ms 38 ms 41.221.166.25
6 * * 151 ms 197.211.35.201
7 * * * Request timed out.
8 170 ms 125 ms 117 ms ldn-b5-link.telia.net [62.115.33.73]
9 142 ms 134 ms 119 ms ldn-bb2-link.telia.net [80.91.246.146]
10 139 ms 124 ms 133 ms ldn-b7-link.telia.net [80.91.248.93]
11 144 ms 147 ms 124 ms xe-4-2-2.edge3.london1.level3.net [4.68.111.181]

12 * * * Request timed out.
13 229 ms 306 ms 305 ms ae-57-222.ebr2.london1.level3.net [4.69.153.133]

14 * * * Request timed out.
15 252 ms 201 ms 198 ms ae-4-4.ebr1.newyork2.level3.net [4.69.141.18]
16 213 ms 198 ms 194 ms ae-37-37.ebr2.washington1.level3.net [4.69.132.8
9]
17 317 ms 200 ms 197 ms ae-92-92.csw4.washington1.level3.net [4.69.134.1
58]
18 204 ms 319 ms 213 ms ae-4-90.edge2.washington1.level3.net [4.69.149.2
06]
19 201 ms 197 ms 198 ms inmotion-ho.edge2.washington1.level3.net [4.79.2
2.110]
20 202 ms 194 ms 199 ms ecbiz156.inmotionhosting.com [198.46.81.164]

Trace complete.

I will need you help as I need my emails to be synchronised properly to avoid loss to my business.

Thank you.
Warmest regards,
Ndianabasi U
Staff
17,716 Points
2014-08-25 3:49 pm
Hello Ndianabasi,

Sorry for the problems with Outlook. I did notice that you also had a ticket open with our live technical support group. We are a separate response team, so you may see difference in response. When we investigated this issue, we found that your hosting server is located in the Eastern United States, so you're basically routing email across the Atlantic, probably through Europe and then down into Africa. This will result in some delay because of the distance that the data must travel. The delays are normal over this distance and it may require that you change the timeout period for Outlook (to make it longer). If you can do this then I would recommend that you do that.

The delay is not something we can directly fix here due to the distance being traveled. You may want to consider a closer host if you want your Outlook email to operate a little quicker. Other than that, you may also want to consider using Webmail as opposed to Outlook, but that would be your preference.

Apologies that I can not give you a direct fix regarding the issue. Please let us know if you have any further questions or comments.

Regards,
Arnel C.
2014-08-25 4:53 pm
Hello Arn,
Thank you for your help. How do I choose a closer host?
Staff
17,716 Points
2014-08-25 5:18 pm
Hello Ndiana,

I'm basically telling you to look for a different hosting service that would be closer to your geographical location. I'm not sure what services are available to you Africa. You should note that it is possible to split your email service from the web hosting service. Email can be hosted closer to you while maintaining your webhosting service with us. However, I'm only saying this in order to keep you as a customer. In the interests of your users, if your email services require a closer hosting service (so that Outlook stops timing out), then you will need to seek an email or web hosting service closer to you. If your web site customers are closer to the server in the United States, then I recommend keeping the hosted site in the United States as it will give your website customers a better experience.

Regards,
Arnel C.
n/a Points
2014-09-18 7:37 am

why below result shown while i ping to my private nameservers,

for new purches server ?

Ping request could not find host ns1.mydomain.com. Please check the name andtry again.

Staff
10,207 Points
2014-09-18 9:59 am
Hello yogi,

Thank you for your question. I would have to look at your specific nameservers to provide an full answer.

But, make sure you activated your nameservers if they are custom.

That is part of our full guide on using Custom Nameservers.

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

Thank you,
John-Paul
n/a Points
2014-11-04 3:49 am

i used to get approx 140ms ping on my previous host. a Shared hosting, though Datacenter where not at all near my geolocation (German datacenter).I transferred to a VPS on inmotion,it does fullfil all the needs except the ping and hence more loadtime.

its approx 265-280ms currently

D:\Documents and Settings\Cyg_Content3>ping aarogya.inPinging aarogya.in [162.254.149.41] with 32 bytes of data:Reply from 162.254.149.41: bytes=32 time=266ms TTL=52Reply from 162.254.149.41: bytes=32 time=265ms TTL=52Reply from 162.254.149.41: bytes=32 time=280ms TTL=52Reply from 162.254.149.41: bytes=32 time=267ms TTL=52Ping statistics for 162.254.149.41:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 265ms, Maximum = 280ms, Average = 269msD:\Documents and Settings\Cyg_Content3>tracert myaarogya.inTracing route to myaarogya.in [23.235.220.169]over a maximum of 30 hops:  1    <1 ms    <1 ms    <1 ms  192.168.1.1  2    11 ms    14 ms    13 ms  10.170.0.1  3    10 ms    11 ms     9 ms  125.99.127.65  4    38 ms    15 ms    12 ms  203.212.193.90  5    12 ms    18 ms    17 ms  203.212.193.85  6    21 ms    12 ms    14 ms  125.99.99.254  7    11 ms    10 ms    19 ms  125.99.99.253  8    19 ms    12 ms    28 ms  121.241.17.118.static.mumbai-lvsb.vsnl.net.in [121.241.17.118]  9   108 ms   111 ms   110 ms  ix-0-100.tcore1.MLV-Mumbai.as6453.net [180.87.38.5] 10   139 ms   134 ms     *     if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.217.17] 11     *      127 ms   122 ms  if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.217.6] 12   145 ms   135 ms   131 ms  if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.17] 13   259 ms   259 ms   259 ms  80.231.153.66 14     *      272 ms     *     ae-3-80.edge3.LosAngeles1.Level3.net [4.69.144.137] 15     *        *        *     Request timed out. 16   248 ms   270 ms   249 ms  cr1.lax1.us.packetexchange.net [4.71.136.2] 17     *        *        *     Request timed out. 18     *        *        *     Request timed out. 19     *        *        *     Request timed out. 20   247 ms   245 ms   286 ms  vp145s.inmotionhosting.com [192.145.239.102] 21   263 ms   246 ms   267 ms  vps13916.inmotionhosting.com [23.235.220.169]Trace complete.

Staff
20,113 Points
2014-11-04 9:41 am
Hello Karan,

We have a great article on how to read a traceroute. You should take a look at that and it will help you understand how they work. I also see you are coming from India. You say you were getting 140ms with a German datacenter. Our US datacenters are more than twice that far, so it would make sense that the ping average is a bit longer, especially crossing the Pacific. These signals do travel via physical lines over physical distances, so the distance between you and the datacenter will have an impact on the timeframe. Within the same continent, over 100ms may seem a bit slow, but from one side of the world to another, there are things to consider such as distance, and routing through other countries. These can also work against the time. Still, read the article I mentioned and you will have a better understanding.

Kindest Regards,
Scott M
n/a Points
2014-11-07 6:03 am

Hello, this is saimon from gadgetghor.com . But my site is really really so slow. Please tell me how to solve the problem. 

regards
Saimon
Staff
208 Points
2014-11-07 11:40 am
Hello Saimon,

I was able to load your website with no slow issues. Are you still seeing these slow page loads? Have you tried performing a traceroute to your webiste?

Kindest Regards,
TJ Edens

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.

34 Questions & Comments

Post a comment

Back to first comment | top

Need more Help?

Search

Ask the Community!

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

Current Customers

Chat: Click to Chat Now E-mail: support@InMotionHosting.com
Call: 888-321-HOST (4678) Ticket: Submit a Support Ticket

Not a Customer?

Get web hosting from a company that is here to help. Sign up today!