Why is my server slow / how do I run a ping and tracert test? - InMotion Hosting
KnowledgeBase
Tools & Resources
(17) (2) (2) (15) (8) (2) (5) (26) (16) (4) (2) (4) (6) (2) (12) (2) (7) (4) (4) (16) (6) (10) (21) (15) (18) (3) (21) (22) (2) (2) (3) (1) (2) (10) (36) (11) (27) (5) (2) (1) (7) (11) (1) (6)
(3) (7) (1) (7) (15) (7) (6) (25) (10) (22) (1) (5) (2) (1) (4) (5) (1) (12) (12) (2) (2) (21) (7) (4) (11) (18) (21) (12) (3) (9) (7) (4) (3) (6) (26) (22) (9) (4) (102) (12) (59) (6) (15) (8) (4)
&& (97433 hits) (18721 hits) (7828 hits) (6426 hits) (4612 hits) (4428 hits) (2862 hits)&&Why is my server slow / how do I run a ping and tracert test?
Views: 97,433
Published: Jul 17, 2015
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 .
How to Run a Ping / Traceroute Test
In the examples below, you will be asked to ping and . Please
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
to see if you may be experiencing a connectivity problem.
If you are on a Windows computer:
Click your start menu and choose run
Type cmd and click OK
and hit enter
When it is done, type
and hit enter.
When both tests are complete, you will want to copy and paste the results in an email and send them to
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:
If you are on a Mac:
Open Applications and then open Utilities.
Open Terminal.
and hit enter. Stop the ping after 4 or 5 results by holding down CTRL-C.
When that is done, type:
and then hit enter.
If you're using an iPad, . There are apps that can help, such as . If you have helpful information about how to ping / tracert from an ipad, !
What to do after you have run the tests:
We have a full guide on "" to help you decide if it needs to be forwarded to Support.
When both tests are complete, you can also copy and paste the results in an email and send them to . 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:
Support Center Login
Remember Me
Social Media Login
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!
Daniels-MacBook-Pro:Downloads daniel$ ping .br
.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
--- .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 .br
traceroute .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& .br (186.220.24.1)& 28.613 ms& 28.872 ms& 30.086 ms
&3& .br (201.6.0.95)& 10.085 ms& 12.785 ms& 9.452 ms
&4& .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
It appears that you are having a bit of latency from the beginning, but completely time out at the datacenter.
I recommend
with this information as your IP may be blocked.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. &All rights reserved.
C:\Users\user&
[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&
Tracing route
[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
It looks like you did not replace < 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.
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.
Hello kat,
When you perform the Ping/Tracert, replace the words "" with your real web address. For example if your website
you would enter:
If you have any further questions, feel free to post them below.
Thank you,
-John-Paul
it is really nice and helpful&
(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
Tracing route
[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. [205.178.152.6]
14 & &413ms &413ms & &** & & & w2k3-web6. [205.178.152.6]
13 & &311ms &312ms & 313ms &w2k3-web6. [205.178.152.6]
Hello Ken,
I am seeing a lot of latency starting on the 5 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
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.
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!
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,
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.
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:
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.
Switzerland
distance from Sweden
distance from Sweden x2
time the packets traveled (RTT)
number of hops
2 x distance/RTT = v
million m/s
distance/number of hops
ping value
ping value
ping value
ping value
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?
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,
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 & [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.
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
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
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.
Can you tell me how you were able to determine all that for Rabbani's issues on 6/25/14 just by looking at his ping and traceroute information?& Is there a tool out there that I can use to do the same thing?&
Thank you in advance,
Hello Hanna,
Thank you for contacting us. Sorry for the delayed response. Most of the information Jacob provides is from running a site scan in . Clicking the "Recommendations" will provide additional details on your results.
Thank you,
I hav ea problem with my client
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.
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.
C:\Users\admin& [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 Tracing route to
[192.145.237.216]over a maximum of 30 hops:& 1&&& 10 ms&&& 34 ms&&& 15 ms& cm1..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&
[173.247.246.116]&13&& 206 ms&& 222 ms&& 194 ms&
[192.145.237.216]Trace complete.C:\Users\admin&
It looks like you are getting some latency within your ISP.
I recommend contacting them for further information.
Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation.& All rights reserved.C:\Users\maku&Tracing route
[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&
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
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,
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:
.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
Tracing route .ng [198.46.81.164]
over a maximum of 30 hops:
homerouter.cpe [192.168.1.1]
Request timed out.
10.200.15.1
41.221.166.33
41.221.166.25
197.211.35.201
Request timed out.
ldn-b5-link.telia.net [62.115.33.73]
ldn-bb2-link.telia.net [80.91.246.146]
ldn-b7-link.telia.net [80.91.248.93]
xe-4-2-2.edge3.london1.level3.net [4.68.111.181]
Request timed out.
ae-57-222.ebr2.london1.level3.net [4.69.153.133]
Request timed out.
ae-4-4.ebr1.newyork2.level3.net [4.69.141.18]
ae-37-37.ebr2.washington1.level3.net [4.69.132.8
ae-92-92.csw4.washington1.level3.net [4.69.134.1
ae-4-90.edge2.washington1.level3.net [4.69.149.2
inmotion-ho.edge2.washington1.level3.net [4.79.2
[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
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
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.
Hello Arn,
Thank you for your help. How do I choose a closer host?
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.
why below result shown while i ping to my private nameservers,
for new purches server ?
Ping request could not find host . Please check the name andtry again.
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
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,
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&
[192.145.239.102]&21&& 263 ms&& 246 ms&& 267 ms&
[23.235.220.169]Trace complete.
Hello Karan,
We have a great article on . 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,
Hello, this is saimon
. But my site is really really so slow. Please tell me how to solve the problem.&
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,
My site can be very slow at times, but every other website i visit seems fast.
PING ww2game.co.uk (198.12.156.62): 56 data bytes
64 bytes from 198.12.156.62: icmp_seq=0 ttl=51 time=189.022 ms
64 bytes from 198.12.156.62: icmp_seq=1 ttl=51 time=185.781 ms
64 bytes from 198.12.156.62: icmp_seq=2 ttl=51 time=180.556 ms
64 bytes from 198.12.156.62: icmp_seq=3 ttl=51 time=185.310 ms
64 bytes from 198.12.156.62: icmp_seq=4 ttl=51 time=191.735 ms
64 bytes from 198.12.156.62: icmp_seq=5 ttl=51 time=188.583 ms
64 bytes from 198.12.156.62: icmp_seq=6 ttl=51 time=177.315 ms
64 bytes from 198.12.156.62: icmp_seq=7 ttl=51 time=182.106 ms
--- ww2game.co.uk ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 177.315/185.051/191.735/4.503 ms
Larss-MacBook-Pro:~ lars-kamfjord$ traceroute ww2game.co.uk
traceroute to ww2game.co.uk (198.12.156.62), 64 hops max, 52 byte packets
&1& 10.0.0.138 (10.0.0.138)& 118.747 ms& 9.671 ms& 9.847 ms
&2& ti-gw.ti.telenor.net (88.91.161.1)& 19.680 ms& 17.063 ms& 12.575 ms
&3& ti-ae1-0.ti.telenor.net (146.172.101.53)& 31.430 ms& 29.769 ms& 19.785 ms
&4& ti-ae4-0.ti.telenor.net (146.172.100.129)& 30.109 ms& 29.930 ms& 29.902 ms
&5& ti-ae5-0.ti.telenor.net (146.172.100.38)& 30.067 ms& 29.616 ms& 19.930 ms
&6& ti-ae0-0.ti.telenor.net (146.172.105.2)& 30.157 ms& 28.830 ms& 30.735 ms
&7& ae51.bar1.copenhagen1.level3.net (213.242.108.13)& 27.066 ms& 29.594 ms& 50.060 ms
10& 4.34.191.254 (4.34.191.254)& 199.660 ms& 189.623 ms& 189.941 ms
11& be38.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.69)& 186.885 ms& 176.227 ms& 185.389 ms
12& be38.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.69)& 190.029 ms
& & be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73)& 187.251 ms& 189.610 ms
13& ip-208-109-112-121.ip.secureserver.net (208.109.112.121)& 190.298 ms& 209.783 ms& 189.377 ms
14& ip-198.12-156-62.ip.secureserver.net (198.12.156.62)& 190.585 ms& 180.763 ms& 188.424 ms
Hello Lars,
for you to be able to determine whether you want to contact your Support or not, however, it appears that you have a bit of latency as you cross the ocean from Copenhagen. The times from there connecting to GoDaddy's servers do not appear to be problematic.
Kindest Regards,
Last login: Thu Nov 20 18:35:27 on console
Melis-MacBook-Pro:~ meliruiz$
(23.235.213.95): 56 data bytes
64 bytes from 23.235.213.95: icmp_seq=0 ttl=246 time=72.902 ms
64 bytes from 23.235.213.95: icmp_seq=1 ttl=246 time=74.762 ms
64 bytes from 23.235.213.95: icmp_seq=2 ttl=246 time=72.997 ms
64 bytes from 23.235.213.95: icmp_seq=3 ttl=246 time=73.622 ms
64 bytes from 23.235.213.95: icmp_seq=4 ttl=246 time=74.154 ms
64 bytes from 23.235.213.95: icmp_seq=5 ttl=246 time=100.491 ms
64 bytes from 23.235.213.95: icmp_seq=6 ttl=246 time=73.786 ms
64 bytes from 23.235.213.95: icmp_seq=7 ttl=246 time=73.176 ms
64 bytes from 23.235.213.95: icmp_seq=8 ttl=246 time=73.048 ms
64 bytes from 23.235.213.95: icmp_seq=9 ttl=246 time=70.436 ms
64 bytes from 23.235.213.95: icmp_seq=10 ttl=246 time=72.088 ms
64 bytes from 23.235.213.95: icmp_seq=11 ttl=246 time=74.066 ms
64 bytes from 23.235.213.95: icmp_seq=12 ttl=246 time=75.657 ms
ping statistics ---
13 packets transmitted, 13 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 70.436/75.476/100.491/7.323 ms
Melis-MacBook-Pro:~ meliruiz$
traceroute
(23.235.213.95), 64 hops max, 52 byte packets
192.168.50.1 (192.168.50.1)
3.952 ms *
l300.washdc-vfttp-126.verizon-gni.net (173.79.95.1)
g0-8-3-5.washdc-lcr-21.verizon-gni.net (130.81.49.42)
ae1-0.res-bb-rtr1.verizon-gni.net (130.81.209.206)
so-12-1-0-0.res-bb-rtr1.verizon-gni.net (130.81.151.230)
ae3-0.res-bb-rtr1.verizon-gni.net (130.81.199.130)
* * ae17.edge1.washingtondc12.level3.net (4.68.62.137)
ae-4-90.edge3.losangeles1.level3.net (4.69.144.201)
0.ae1.br2.iad8.alter.net (140.222.229.167)
* ae17.edge1.washingtondc12.level3.net (4.68.62.137)
cr1.lax1.us.packetexchange.net (4.71.136.2)
ae-3-80.edge3.losangeles1.level3.net (4.69.144.137)
67.437 ms *
* ae-1-60.edge3.losangeles1.level3.net (4.69.144.9)
74.760 ms *
cr1.lax1.us.packetexchange.net (4.71.136.2)
23.235.213.95 (23.235.213.95)
Hello Melihector,
From what I can see with your traceroute, there should not be a connection problem. All the times are good. You can learn more about the traceroute and .
If your site is running slow, please
so they can look further into your specific account.
Kindest Regards,
Our web application is having great latency for each changing page. (e.g.: Each hyperlink clicked causes a wait time of few seconds before it loads). Thank you.
My IP during ping and tracrt test:&60.50.223.96
[216.194.175.95] with 32 bytes of data:
Reply from 216.194.175.95: bytes=32 time=327ms TTL=52
Reply from 216.194.175.95: bytes=32 time=324ms TTL=52
Reply from 216.194.175.95: bytes=32 time=324ms TTL=52
Reply from 216.194.175.95: bytes=32 time=325ms TTL=52
Ping statistics for 216.194.175.95:
& & Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
& & Minimum = 324ms, Maximum = 327ms, Average = 325ms
Tracing route
[216.194.175.95]
over a maximum of 30 hops:
TRACERT TEST
& 1 & & 3 ms & & 1 ms & & 4 ms &192.168.0.1
& 2 & & 2 ms & & 4 ms & & 7 ms &192.168.1.1
& 3 & &43 ms & &25 ms & &26 ms &175.137.110.22
& 4 & & * & & & &* & & & &* & & Request timed out.
& 5 & & * & & & &* & & & &* & & Request timed out.
& 6 & & * & & & &* & & & &* & & Request timed out.
& 7 & & * & & & &* & & & &* & & Request timed out.
& 8 & & * & & & &* & & & &* & & Request timed out.
& 9 & & * & & & &* & & & &* & & Request timed out.
&10 & & * & & & &* & & & &* & & Request timed out.
Hello Simon,
Your traceroute shows that the last IP it was able to receive a response from is 175.137.110.22, which is Malaysia, Kuala Lumpur. Beyond that, everything times out. It appears that may be the problem. Be sure to check out our article on
for more information.
Kindest Regards,
My website is very slow. Can you any one please help me to solve this issue? Whether this is from hosting problem or code issue?
Below are the trace and ping details of my website. [ http://goo.gl/SQiHdE ]
C:\Users\karthik&
[74.125.68.113] with 32 bytes of data:
Reply from 74.125.68.113: bytes=32 time=58ms TTL=48
Reply from 74.125.68.113: bytes=32 time=162ms TTL=48
Reply from 74.125.68.113: bytes=32 time=60ms TTL=48
Reply from 74.125.68.113: bytes=32 time=64ms TTL=48
Ping statistics for 74.125.68.113:
& & Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
& & Minimum = 58ms, Maximum = 162ms, Average = 86ms
C:\Users\karthik&tracert fashion4decision.de
Tracing route to fashion4decision.de [212.1.212.192]
over a maximum of 30 hops:
& 1 & & 4 ms & & 6 ms & & 2 ms &172.16.1.1
& 2 & &25 ms & &48 ms & &45 ms &182.73.157.249
& 3 & &36 ms & &80 ms & &41 ms &182.79.237.194
& 4 & 159 ms & 157 ms & 235 ms &182.79.245.14
& 5 & 286 ms & 279 ms & 283 ms &mei-b1-link.telia.net [213.248.93.9]
& 6 & 295 ms & 291 ms & 302 ms &prs-bb2-link.telia.net [80.91.248.152]
& 7 & 272 ms & 316 ms & 280 ms &ash-bb4-link.telia.net [80.91.254.214]
& 8 & 355 ms & 293 ms & 348 ms &cha-b1-link.telia.net [213.155.137.115]
& 9 & 319 ms & 280 ms & 322 ms &giglinx-ic-156088-cha-b1.c.telia.net [213.248.68
&10 & 336 ms & 278 ms & 267 ms &67.23.161.157
&11 & 305 ms & 298 ms & 292 ms &67.23.161.129
&12 & 256 ms & 288 ms & 272 ms &ashv1. [208.69.231.10]
&13 & 284 ms & 281 ms & 305 ms &srv212- [212.1.212.192]
Trace complete.
C:\Users\karthik&
Hello Karthik,
Sorry for the problem with your website.
Unfortunately, since you are not hosted with us, we can't really use the traceroute to determine why you're having problems.
We would generally be investigating the issue in terms of how you're connecting to our servers.
If you look at your traceroute, you can determine that you start seeing triple digit connection times at a particular point.
You may want to contact your host or internet service provider and ask why the connection has slowed at that point.
I hope that helps to provide you a direction to help resolve your problem.
Apologies that we can't help you resolve the issue directly.
Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\Users\hoang&pinghttp://rez1.bangbang.cgame.vn/index/?sign=c3c3796ebe3e704d88b5c4f623228dba'pinghttp:' is not recognized as an internal or external command,operable program or batch file.C:\Users\hoang&pinghttp://rez1.bangbang.cgame.vn'pinghttp:' is not recognized as an internal or external command,operable program or batch file.C:\Users\hoang&ping http://rez1.bangbang.cgame.vnPing request could not find host http://rez1.bangbang.cgame.vn. Please check the&name and try again.C:\Users\hoang&pingrez1.bangbang.cgame.vn'pingrez1.bangbang.cgame.vn' is not recognized as an internal or external command,operable program or batch file.C:\Users\hoang&ping rez1.bangbang.cgame.vnPinging
[113.164.15.234] with 32 bytes of data:Reply from 113.171.8.30: Destination net unreachable.Reply from 113.171.8.30: Destination net unreachable.Reply from 113.171.8.30: Destination net unreachable.Reply from 113.171.8.30: Destination net unreachable.Ping statistics for 113.164.15.234:&&& Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),C:\Users\hoang&tracert rez1.bangbang.cgame.vnTracing route to
[113.164.15.234]over a maximum of 30 hops:& 1&&&& 1 ms&&&& 2 ms&&&& 2 ms&
[192.168.1.1]& 2&& 841 ms&& 362 ms&& 459 ms& 10.9.101.1& 3& 1209 ms& 1121 ms&&&& *&&&& G0-5-4-2.BSTNMA-LCR-22.verizon-gni.net [130.81.195.172]& 4&& 499 ms&& 409 ms&& 876 ms& ae10-0.BOS-BB-RTR2.verizon-gni.net [130.81.163.172]& 5& 1166 ms& 1260 ms& 1282 ms& 0.ae11.XL4.NYC1.ALTER.NET [152.63.20.117]& 6&&&& *&&&&&&& *&&&&&&& *&&&& Request timed out.& 7&& 820 ms&& 952 ms& 1024 ms& 3.et-2-0-1.TL2.NYC1.ALTER.NET [140.222.227.34]& 8& 1049 ms& 1026 ms&&&& *&&&& TenGigE0-7-0-9.GW8.NYC4.ALTER.NET [152.63.18.206]& 9&& 427 ms&& 467 ms&& 489 ms& tinet-gw.customer.alter.net [152.179.72.122]&10&& 604 ms&& 702 ms&& 994 ms& xe-2-0-2.lax21.ip4.gtt.net [141.136.110.197]&11& 1805 ms&& 653 ms&& 402 ms& singapore-telecommunications-gw.ip4.gtt.net [46.33.80.34]&12&& 898 ms&& 615 ms& 1285 ms& 203.208.171.141&13& 1174 ms& 1350 ms& 1307 ms& 203.208.178.185&14& 1185 ms& 1100 ms& 1295 ms& 203.208.158.10&15&& 502 ms&& 541 ms&& 629 ms& 203.208.153.253&16&& 699 ms&& 725 ms&& 711 ms& 203.208.153.198&17&& 680 ms&& 725 ms&& 741 ms& 203.208.192.178&18&&&& *&&&& 2097 ms&&&& *&&&& 203.208.153.198&19&&&& *&&&&& 424 ms& 1450 ms& simon [113.171.8.30]&20& simon [113.171.8.30]& reports: Destination net unreachable.Trace complete.C:\Users\hoang&C:\Users\hoang&
Hello Hoang,
From the posted information it appears that the issues start from within your own network. They continue to grow from there with the first out of network hop, which appears to be somewhere near Boston, Massachusetts. You can always take a look at your own ping and trace by following our article on .
Kindest Regards,
Here is the info from our ping test and tracer test. Can you help us, too? We have battled for two weeks and can get no downloads from servers that are on the other side of our country or outside of the country. This includes Java, Norton, and Steam.
Here is the data.
I cannot copy the data so I have emailed it to your support email address. Please look there and help us.
Hello Gail,
Thank you for your question. Here is a link to our helpful guide on .
We are happy to help review yours, but will need to see the results of your Ping/Tracert. Since our Live Support department is for current customers, you will have to paste your results here.
Thank you,
traceroute .uy (23.235.211.68), 64 hops max, 72 byte packets
(192.168.1.1)& 11.990 ms& 1.021 ms& 0.953 ms
&2& cor2bras1.antel.net.uy (200.40.161.195)& 4.192 ms& 4.033 ms& 4.427 ms
&3& ibb2cor4-0-2-0-0.antel.net.uy (200.40.161.14)& 5.060 ms& 4.096 ms& 3.257 ms
&4& cbb2tia1-be200.antel.net.uy (200.40.78.5)& 5.937 ms& 9.387 ms& 6.077 ms
&5& ibe2agu1-be200.antel.net.uy (200.40.78.6)& 7.374 ms& 7.598 ms& 3.978 ms
&6& ibr2nap3-0-2-1-0.antel.net.uy (200.40.16.174)& 160.638 ms& 159.368 ms& 160.254 ms
&7& * * xe-9-3-2.edge4.miami1.level3.net (4.59.90.45)& 180.277 ms
&8& ae-2-70.edge3.losangeles1.level3.net (4.69.144.73)& 389.254 ms&
10& cr1.lax1.us.packetexchange.net (4.71.136.2)& 263.111 ms& 305.847 ms& 228.844 ms
14& 23.235.211.68 (23.235.211.68)& 514.515 ms& 306.565 ms& 306.636 ms
Hello Alan,
It appears your delays start around an IP in Uraguay starting at hop 6. You can learn more about this type of issue from our article on .
Kindest Regards,
This is my ping/tracerout test
Please help, why is my internet not working right?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\Pinguin&
Ping wird ausgef&hrt f& [93.184.216.34] mit 32 Bytes Daten:
Antwort von 93.184.216.34: Bytes=32 Zeit=9ms TTL=59
Antwort von 93.184.216.34: Bytes=32 Zeit=9ms TTL=59
Antwort von 93.184.216.34: Bytes=32 Zeit=8ms TTL=59
Antwort von 93.184.216.34: Bytes=32 Zeit=9ms TTL=59
Ping-Statistik f&r 93.184.216.34:
& & Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
& & (0% Verlust),
Ca. Zeitangaben in Millisek.:
& & Minimum = 8ms, Maximum = 9ms, Mittelwert = 8ms
C:\Users\Pinguin&
Routenverfolgung
[93.184.216.34] &ber maximal 30 Abschnitte:
& 1 & & 3 ms & & 3 ms & & 3 ms &Wireless_Broadband_Router.home [192.168.1.1]
& 2 & &10 ms & & 8 ms & & 7 ms &lo0-100.WASHDC-VFTTP-305.verizon-gni.net [108.31
& 3 & &10 ms & &11 ms & &10 ms &T1-4-0-3.WASHDC-LCR-22.verizon-gni.net [100.41.1
& 4 & & * & & & &* & & & &* & & Zeit&berschreitung der Anforderung.
& 5 & & * & & & &* & & & &* & & Zeit&berschreitung der Anforderung.
& 6 & & 9 ms & & 8 ms & & 8 ms &0.ae4.GW1.IAD6.ALTER.NET [140.222.230.107]
& 7 & & 9 ms & & 8 ms & & 8 ms &.customer.alter.net [204.148.3.62]
& 8 & & 9 ms & & 8 ms & & 9 ms &93.184.216.34
Ablaufverfolgung beendet.
C:\Users\Pinguin&
Hello Atom,
Your ping and trace do not look like there is any connection issue. You can take a look at out
for more information,.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\user&
'' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\user&
'' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\user&
'' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\user&ping
[97.74.118.146] with 32 bytes of data:
Reply from 97.74.118.146: bytes=32 time=366ms TTL=49
Reply from 97.74.118.146: bytes=32 time=374ms TTL=49
Reply from 97.74.118.146: bytes=32 time=354ms TTL=49
Reply from 97.74.118.146: bytes=32 time=377ms TTL=49
Ping statistics for 97.74.118.146:
& & Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
& & Minimum = 354ms, Maximum = 377ms, Average = 367ms
C:\Users\user&tracert
Tracing route to
[97.74.118.146]
over a maximum of 30 hops:
& 1 & & 1 ms & &&1 ms & & 1 ms &192.168.0.1
& 2 & &72 ms & &77 ms & &70 ms &10.139.1.1
& 3 & &19 ms & &20 ms & &16 ms &10.120.1.1
& 4 & &26 ms & &27 ms & &19 ms &nsg-static-001.172.72.182.airtel.in [182.72.172.
& 5 & &74 ms & &75 ms & &73 ms &202.123.44.89
& 6 & &46 ms & &59 ms & &47 ms &125.62.148.5
& 7 & &57 ms & &64 ms & &54 ms &182.79.234.133
& 8 & &44 ms & &46 ms & &51 ms &182.79.234.134
& 9 & 309 ms & 320 ms & 312 ms &182.79.245.149
&10 & 299 ms & 289 ms & 304 ms &lap-brdr-03.inet.qwest.net [63.146.26.233]
&11 & & * & & & &* & & & &* & & Request timed out.
&12 & 295 ms & 307 ms & 310 ms &63-232-81-254.dia.static.qwest.net [63.232.81.25
&13 & 356 ms & 360 ms & 362 ms &ip-97-74-253-94.ip.secureserver.net [97.74.253.9
&14 & 365 ms & 360 ms & 368 ms &ip-97-74-253-94.ip.secureserver.net [97.74.253.9
&15 & 347 ms & 341 ms & 348 ms &ip-97-74-253-98.ip.secureserver.net [97.74.253.9
&16 & 298 ms & 295 ms & 295 ms &ip-208-109-113-174.ip.secureserver.net [208.109.
&17 & 363 ms & 369 ms & 372 ms &ip-97-74-118-146.ip.secureserver.net [97.74.118.
Trace complete.
C:\Users\user&
The trace seems to run into trouble at around hop 9. That IP address (182.79.245.149) is listed as being in Dehli, India. From that hop forward, you can see that the times are consistently higher. This indicates that the issue is likely with the router on hop 9. Unless that router is owned by you, your ISP, or hosting company, then you will have no direct control or be able to correct the issue. You will need to wait until the owner of the router corrects the problem, then you should no longer have the delays on the affected hops.
Kindest Regards,
unacceptabl perfromnace to from Europe.
& 1 & &&1 ms & &&1 ms & &&1 ms &192.168.1.1
& 2 & & 1 ms & &&1 ms & &&1 ms &192.168.2.1
& 3 & &26 ms & &25 ms & &25 ms &217.5.98.13
& 4 & &26 ms & &26 ms & &27 ms &217.237.154.30
& 5 & &26 ms & &25 ms & &26 ms &62.157.249.78
& 6 & & * & & & &* & & & &* & & Request timed out.
& 7 & 119 ms & 119 ms & 119 ms &INMOTION-HO.ear3.Washington1.Level3.net [4.79.22
& 8 & & * & & & &* & & & &* & & Request timed out.
& 9 & & * & & & &* & & & &* & & Request timed out.
&10 & 123 ms & 123 ms & 123 ms & [198.46.81.92]
&11 & 123 ms & 124 ms & 123 ms & [198.46.86.157]
Trace complete.
The available
timestamps in your traceroute seem to be reasonable. Are you getting packet loss on your ping?
Thank you,
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. &All rights reserved.
C:\Users\BoonFair&tracert boonfair.lk
Tracing route to boonfair.lk [199.223.115.74]
over a maximum of 30 hops:
& 1 & & * & & & &* & & & &* & & Request timed out.
& 2 & & * & & & &* & & & &* & & Request timed out.
& 3 & & * & & & &* & & & &* & & Request timed out.
& 4 & & * & & & &* & & & &* & & Request timed out.
& 5 & 133 ms & &79 ms & &79 ms &202.129.235.132
& 6 & 641 ms & 209 ms & 359 ms &212.73.201.1
& 7 & & * & & & &* & & & &* & & Request timed out.
& 8 & 323 ms & 299 ms & 299 ms &INMOTION-HO.ear3.Washington1.Level3.net [4.79.22
& 9 & & * & & & &* & & & &* & & Request timed out.
&10 & & * & & & &* & & & &* & & Request timed out.
&11 & 314 ms & 469 ms & 559 ms &eccomp12- [104.193.140.
&12 & 607 ms & 480 ms & 319 ms & [199.223.115.74]
Trace complete.
C:\Users\BoonFair&ping boonfair.lk
Pinging boonfair.lk [199.223.115.74] with 32 bytes of data:
Reply from 199.223.115.74: bytes=32 time=597ms TTL=53
Reply from 199.223.115.74: bytes=32 time=306ms TTL=53
Reply from 199.223.115.74: bytes=32 time=304ms TTL=53
Reply from 199.223.115.74: bytes=32 time=582ms TTL=53
Ping statistics for 199.223.115.74:
& & Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
& & Minimum = 304ms, Maximum = 597ms, Average = 447ms
C:\Users\BoonFair&
Hello Nuwan,
Sorry for the problems with connecting to the server.
In looking at your traceroute appears there are issues early in the trace.
You are starting with 3 digits times.
This could be a temporary issue, but it is an issue that most likely comes from your ISP.
If you consistently get the same times after 24 hours, then please
that includes your latest traceroute and description of the problem that you're having.
They can investigate it further and determine if we can make a corrective action on our end.
If you have any further questions or comments, please let us know.
Need more Help?
Ask the Community!
Get help with your questions from our community of like-minded hosting users and InMotion Hosting Staff.
Current Customers
888-321-HOST (4678)
Not a Customer?
from a company that is here to help.
Stay in touch on
6100 Center Drive, Suite 1190
Los Angeles, CA 90045
888.321.HOST(4678)
2016 (C) All Rights Reserved