InMotion Hosting Support Center

In this tutorial:

There are times when it seems your website may respond slowly. Slow response time may indicate a problem. Most just assume the server is overloaded and call their technical support. Many times, the support representative will ask for a ping and traceroute report. While we have instructions on running this report, it can seem rather cryptic when looking at it.

It doesn't take a degree or any kind of special training to decode a traceroute report. In fact, we will teach you how in this article. This way, if you ever have slow response from your site, you can run a report and quickly determine whether you need to contact our Live Support team.

How a Traceroute works

Whenever a computer connects to a website, it must travel a path that consists of several points, a little like connecting the dots between your computer and the website. The signal starts at your local router in your home or business, then moves out to your ISP, then onto the main networks. From there it may have several junctions until it gets off the Internet highway at the local network for the website and then to the webserver itself.

A traceroute displays the path that the signal took as it traveled around the Internet to the website. It also displays times which are the response times that occurred at each stop along the route. If there is a connection problem or latency connecting to a site, it will show up in these times. You will be able to identify which of the stops (also called 'hops') along the route is the culprit.

How to read a Traceroute

Once the traceroute is run, it generates the report as it goes along the route. Below is a sample traceroute:

C:\>tracert www.example.com
Tracing route to example.com [10.10.242.22]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  172.16.10.2
  2     *        *        *     Request timed out.
  3     2 ms     2 ms     2 ms  vbchtmnas9k02-t0-4-0-1.coxfiber.net [216.54.0.29]
  4    12 ms    13 ms     3 ms  68.10.8.229
  5     7 ms     7 ms     7 ms  chndbbr01-pos0202.rd.ph.cox.net [68.1.0.242]
  6    10 ms     8 ms     9 ms  ip10-167-150-2.at.at.cox.net [70.167.150.2]
  7    10 ms     9 ms    10 ms  100ge7-1.core1.nyc4.he.net [184.105.223.166]
  8    72 ms    84 ms    74 ms  10gr10-3.core1.lax1.he.net [72.52.92.226]
  9    76 ms    76 ms    90 ms  10g1-3.core1.lax2.he.net [72.52.92.122]
 10    81 ms    74 ms    74 ms  205.134.225.38
 11    72 ms    71 ms    72 ms  www.inmotionhosting.com [192.145.237.216]

As you can see, there are several rows divided into columns on the report. Each row represents a "hop" along the route. Think of it as a check-in point where the signal gets its next set of directions. Each row is divided into five columns. A sample row is below:

10    81 ms    74 ms    74 ms  205.134.225.38

Let's break this particular hop down into its parts.

Hop # RTT 1 RTT 2 RTT 3 Name/IP Address
10 81 ms 74 ms 74 ms 205.134.225.38

Hop Number - This is the first column and is simply the number of the hop along the route. In this case, it is the tenth hop.

RTT Columns - The next three columns display the round trip time (RTT) for your packet to reach that point and return to your computer. This is listed in milliseconds. There are three columns because the traceroute sends three separate signal packets. This is to display consistency, or a lack thereof, in the route.

Domain/IP column - The last column has the IP address of the router. If it is available, the domain name will also be listed.

Checking the hop times

The times listed in the RTT columns are the main thing you want to look at when evaluating a traceroute. Consistent times are what you are looking for. There may be specific hops with increased latency times but they may not indicate that there is an issue. You need to look at a pattern over the whole report. Times above 150ms are considered to be long for a trip within the continental United States. (Times over 150ms may be normal if the signal crosses an ocean, however.) but issues may show up with very large numbers.

Increasing latency towards the target

If you see a sudden increase in a hop and it keeps increasing to the destination (if it even gets there), then this indicates an issue starting at the hop with the increase. This may well cause packet loss where you will even see asterisks (*) in the report.
  1    10 ms     7 ms     9 ms  172.16.10.2
  2    78 ms   100 ms    32 ms  ip10-167-150-2.at.at.cox.net [70.167.150.2]
  3    78 ms    84 ms    75 ms  100ge7-1.core1.nyc4.he.net [184.105.223.166]
  4   782 ms   799 ms     * ms  10gr10-3.core1.lax1.he.net [72.52.92.226]
  5     * ms   899 ms   901 ms  10g1-3.core1.lax2.he.net [72.52.92.122]
  6   987 ms   954 ms   976 ms  205.134.225.38
  7  1002 ms  1011 ms   999 ms  www.inmotionhosting.com [192.145.237.216]

High latency in the middle but not at beginning or end

If the hop immediately after a long one drops back down, it simply means that the router at the long hop set the signal to a lower priority and does not have an issue. Patterns like this do not indicate an issue.

1  <1 ms     <1 ms       <1 ms 173.247.246.116
2  30 ms      7 ms       11 ms 10.10.0.2
3 200 ms    210 ms      189 ms 4.71.136.1
4 111 ms     98 ms      101 ms ip10-167-150-2.at.at.cox.net [70.167.150.2]
5  99 ms    100 ms       98 ms  205.134.225.38

High latency in the middle that remains consistent

If you see a hop jump but remain consistent throughout the rest of the report, this does not indicate an issue.

1  <1 ms     <1 ms       <1 ms 173.247.246.116
2  30 ms      7 ms       11 ms 10.10.0.2
3  93 ms     95 ms       92 ms 4.71.136.1
4  95 ms     99 ms      101 ms ip10-167-150-2.at.at.cox.net [70.167.150.2]
5  99 ms    100 ms       98 ms 100ge7-1.core1.nyc4.he.net [184.105.223.166]
6  95 ms     95 ms       95 ms 10g1-3.core1.lax2.he.net [72.52.92.122]
7  95 ms     96 ms       94 ms 205.134.225.38]

High latency in the beginning hops

Seeing reported latency in the first few hops indicates a possible issue on the local network level. You will want to work with your local network administrator to verify and fix it.

Timeouts at the beginning of the report

If you have timeouts at the very beginning of the report, say within the first one or two hops, but the rest of the report runs, do not worry. This is perfectly normal as the device responsible likely does not respond to traceroute requests.

Timeouts at the very end of the report

Timeouts at the end may occur for a number of reasons. Not all of them indicate an issue, however.

  • The target's firewall may be blocking requests. The target is still most probably reachable with a normal HTTP request, however. This should not affect normal connection.
  • The return path may have an issue from the destination point. This would mean the signal is still reaching, but just not getting the return signal back to your computer. This should not affect normal connection.
  • Possible connection problem at the target. This will affect the connection.

Do I need to contact my hosting company?

Once you have found a hop that seems to have an issue, you can identify its location and determine where the issue lies. It may be within your network, your ISP, somewhere along the route, or within your hosting provider's domain.

The first hop is within your own network. The next hop is your ISP. The last couple of hops are likely within your hosting providers' domain and control, so if the issue is there, they may be able to fix it for you. If it is anywhere prior to that, the issue is simply along the route and is within neither your nor your hosting provider's control.

Support Center Login

Social Media Login

   
Social Login Joomla

Related Questions

Here are a few questions related to this article that our customers have asked:
tracert ending very odd?
Would you like to ask a question about this page? If so, click the button below!
Ask a Question
n/a Points
2014-09-10 11:55 am
IDK, probably the best one I have read and I have read MANY!
Having s SERIOUS issue with latency just on my pc using cable modem connecting to my website. No other website has this issue. Can take 20-30 seconds to load. If I use a proxy server, takes 2-3 seconds.
If I connect to cable modem via WiFi with my Samsung Galaxy S5, go to website, problem is there. If I kill WiFi and connect with AT&T carrier, response to website is 1-3 seconds; not 20-30 when using cable modem.
Now you guys have me interested in your hosting service.
n/a Points
2014-09-12 6:55 am
Oh! Thats 2much anyway.Ur Gr8! Thank you very much.
n/a Points
2015-01-02 10:15 pm
you can't improve it.
I knew nothing at all about tracer routes until I read your article.
Thank you very much.
n/a Points
2015-02-15 11:43 pm

How is the #10 hop number the 6th? Is there a reason that the origional poster didnt specify? Im completely new to this and ive been looking for an hour now about hop numbers and this threw me completely off

Staff
34,772 Points
2015-02-16 3:17 pm
Hello James,

Thanks for the questions. The traceroutes supplied above are samples for the purposes of the tutorial. If you have a specific question about traceroutes, please let us know.

Regards,
Arnel C.

n/a Points
2015-07-29 5:04 pm

Arn, your answer to James regarding the example, 6th vs 10th hop is cavalier at best.

The example is shown specifically, graphically etc. and is wrong. This displays a lack of concern regarding quality and accuracy on your part. If you are wrong in this area, what else are you wrong in?  Show some pride and get it right. 

Staff
34,772 Points
2015-07-29 5:27 pm
Danuke,

Sorry, if my answer wasn't satisfactory to you (and to James). I was simply trying to keep things simple and not introduce more confusion in the issue. The second screenshot was created to provide the scenario that was being explained in the tutorial. I verified this with the author. There is NO correlation between those two screenshots. The tutorial was simply trying to demonstrate a scenario where the hop times all of a sudden showed a large increase in time towards the destination URL/IP address.

If this were to happen real life, the difference in hops simply indicates a different network route to get to the targeted URL/IP address.


Regards,
Arnel C.
n/a Points
2015-02-25 11:50 am
is asterisks the same as n/a , just before my latency goes high , a hop has n/a
Staff
39,779 Points
2015-02-27 10:02 am
Hello JimmyG,

It is not uncommon to have a hop or two in a trace with asterisks. If the asterisks continued throughout the trace and the trace never got to it's destination, that's obviously bad. But one or two hops in there with asterisks could mean that router is not sending responses to pings.

Kindest Regards,
Scott M
n/a Points
2015-02-25 11:54 am

rout has 9 hops , 1st 4 hops around 36 ms , then 5th hop shows n/a , 6th hop jumps to 138ms is that normal

Staff
39,779 Points
2015-02-27 10:03 am
Hello JimmyG,

If the 7th hop was under 100ms, then it is likely that hop 6 set your packet to a lower priority. That would not indicate a traffic or latency issue.

Kindest Regards,
Scott M
n/a Points
2015-04-24 2:15 pm

Have you ever see a tracert end like this below?  The end IP is 192.168.219.140

Any idea what could cause this?

12 * 273 ms * 192.168.219.140

13 * * * Request timed out.

14 261 ms * * 192.168.219.140

15 282 ms * *

 

Staff
34,772 Points
2015-04-24 9:55 pm
Hello Clemson Guy,

The normal reason you'll see a repetition in the trace is due to network configuration. It might be an internal and external portion of the network. The timeout in between is probably the result of a firewall. This is a guess on my part at this point because I'm not familiar with your network configuration. This postalso describes a result similar to yours. If you want further confirmation, then look for a local network engineer, to look at the traceroute for you. You can also submit a ticket request (if you're a customer of InMotion) to the InMotion Hosting live technical support team. They can look at the traceroute result in more depth.

Kindest regards,
Arnel C.
n/a Points
2015-05-03 6:49 pm

I'm having an impossible time connecting to certain sites, one of which is google. I can't connect to facebook or google using chrome or IE , but I can connect to all sites using firefox. Ironically, I can connect to bing using IE and chrome. I suspect that I have some vicious malware because Norton *cough cough* has been losing it's mind, and can't even run NPE now.

Someone suggested that I run a traceroute on google.com to see what was going on, but I don't understand any of these results. Any help is appreciated.C:\Users\XXXXXXK>tracert www.google.comTracing route to www.google.com [74.125.228.244]over a maximum of 30 hops:  1     2 ms     1 ms    <1 ms  192.168.1.1  2    12 ms    28 ms    35 ms  96.120.106.13  3    20 ms     9 ms     9 ms  68.85.112.29  4    12 ms    11 ms    12 ms  xe-7-1-7-0-ar01.whitemarsh.md.bad.comcast.net [68.85.114.213]  5    22 ms    26 ms    19 ms  he-3-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.91.69]  6    15 ms    25 ms    17 ms  he-0-11-0-0-pe02.111eighthave.ny.ibone.comcast.net [68.86.85.18]  7    22 ms    56 ms    16 ms  50-248-116-186-static.hfc.comcastbusiness.net [50.248.116.186]  8    21 ms    17 ms    17 ms  209.85.248.242  9    19 ms    24 ms    18 ms  209.85.249.212 10    32 ms    34 ms    31 ms  216.239.40.158 11    19 ms    17 ms    23 ms  72.14.236.153 12   119 ms    17 ms    18 ms  72.14.233.95 13    22 ms    18 ms    19 ms  iad23s24-in-f20.1e100.net [74.125.228.244]Trace complete.

Staff
39,779 Points
2015-05-04 7:53 am
Hello NB,

I took a look at your traceroute and everything looks fine. There is no indicator of latency or of the signal not making the trip properly. You may have some sort of issue locally or within your browsers. Unfortunately we are unable to assist with local issues. But the trace definitely looks normal.

Kindest Regards,
Scott M
n/a Points
2015-06-10 11:50 am

thanks for the nice article.

when i do a traceroute in my system - i see a lot of "*" beyond 15 hops. however, when i try using http to access the target i am able to do it. Any idea what the problem might be? i read "*" meant loss of data packets. Does a "*" indicate slow network connectivity always?

i see the following

1  192.168.0.1 (192.168.0.1)  2.045 ms  1.619 ms  1.457 ms

 2  ras.beamtele.net (183.83.0.1)  1.947 ms  2.646 ms  1.777 ms

 3  ras.beamtele.net (183.82.14.129)  3.927 ms  2.427 ms  2.337 ms

 4  ras.beamtele.net (183.82.14.221)  2.888 ms  2.905 ms  3.108 ms

 5  121.240.252.37.static-hyderabad.vsnl.net.in (121.240.252.37)  3.171 ms  2.532 ms  3.103 ms

 6  * * *

 7  * * *

 8  * * *

 9  if-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6)  124.681 ms  125.289 ms  128.638 ms

10  if-2-2.tcore1.pvu-paris.as6453.net (80.231.154.17)  124.533 ms  123.979 ms  124.822 ms

11  xe-0-1-0.mpr1.cdg11.fr.zip.zayo.com (64.125.14.57)  121.835 ms  120.686 ms  120.923 ms

12  * * *

13  ae5.cr2.dca2.us.zip.zayo.com (64.125.20.190)  212.859 ms  206.206 ms  214.113 ms

14  xe-0-0-0.mpr1.iad6.us.zip.zayo.com (64.125.28.189)  222.660 ms  217.433 ms  218.426 ms

15  64.125.188.210.t01076-01.above.net (64.125.188.210)  208.801 ms  211.877 ms  216.963 ms

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * * 

--------

64 * * * 

Staff
34,772 Points
2015-06-11 3:45 am
Kumar,

Typically, the *** is indicating a firewall preventing a return in your traceroute. However, if it's timing out repeatedly at the end, then there may be another issue at hand. If you are a customer of InMotion Hosting, please submit the traceroute to our live support team through a support ticket in order to have the issue properly investigated. Otherwise, you will need to have the issue investigated by your ISP or your host's support.

Regards,
Arnel C.
n/a Points
2015-06-19 4:54 pm

 1    <1 ms    <1 ms    <1 ms  192.168.0.1 

  2     8 ms     8 ms    12 ms  10.98.48.1 

  3    60 ms    62 ms    59 ms  192.168.49.65 

  4    19 ms    19 ms    23 ms  10.224.253.13 

  5    58 ms    59 ms    59 ms  10.224.252.1 

  6    59 ms    58 ms    68 ms  xe-4-3-3.bar1.Phoenix1.Level3.net [4.28.81.9] 

  7    82 ms    78 ms    92 ms  ae-1-60.edge8.SanJose1.Level3.net [4.69.152.20] 

  8    79 ms    88 ms    98 ms  ae-1-60.edge8.SanJose1.Level3.net [4.69.152.20] 

  9    79 ms    78 ms    87 ms  4.35.70.82 

 10    78 ms    78 ms    79 ms  104.160.130.44 

 11    97 ms    97 ms    95 ms  104.160.159.6 

 12    96 ms    97 ms    95 ms  104.160.159.0 

 13    97 ms    97 ms    96 ms  104.160.128.101 

 

This is my traceroute to a game server thats in portland oregon (I live in Idaho) what can I do to get my ISP to put me on a priority line because it hasn't always been like this... they keep telling me they have no control over their own routing.

Staff
25,021 Points
2015-06-22 3:02 pm
Hello Jordan,

Thank you for contacting us. Once your ISP leaves the Data Center they are essentially at the mercy of the backbone they are using, since there are a limited amount of lines connecting some areas.

A better approach may be to perform a traceroute at the time you are experiencing issues. This will provide specific evidence that you can forward to your ISP.

They should then be able to contact their backbone provider and address the route problem.

Thank you,
John-Paul
n/a Points
2015-07-19 7:13 pm

I live in North Dakota and am experinacing high latency connecting to XBOX, ISP says its XBOX and XBOX says its ISP. Here is what I get when i tun trace route

Traceroute has started…

 

traceroute to 65.55.42.1 (65.55.42.1), 64 hops max, 72 byte packets

 1  hitronhub.home (192.168.0.1)  1.045 ms  0.666 ms  1.052 ms

 2  * * *

 3  host-173-6-220-24-static.midco.net (24.220.6.173)  11.132 ms  10.323 ms  10.060 ms

 4  host-41-182-220-24-static.midco.net (24.220.182.41)  21.068 ms  20.242 ms  26.324 ms

 5  host-113-182-220-24-static.midco.net (24.220.182.113)  25.176 ms  23.304 ms  23.295 ms

 6  chi-8075.msn.net (206.223.119.27)  214.619 ms  217.187 ms  214.597 ms

 7  ae12-0.ch1-96c-2a.ntwk.msn.net (207.46.40.215)  223.046 ms  227.141 ms  217.488 ms

 8  * * *

 9  * * *

10  ae9-0.co2-96c-1a.ntwk.msn.net (191.234.82.236)  218.566 ms  214.333 ms  213.881 ms

11  134.170.8.225 (134.170.8.225)  213.599 ms  216.126 ms  214.015 ms

12  10.10.3.170 (10.10.3.170)  214.177 ms  215.225 ms  214.000 ms

13  10.10.3.214 (10.10.3.214)  215.676 ms  215.787 ms  218.094 ms

14  25.255.12.94 (25.255.12.94)  232.149 ms  214.606 ms  215.554 ms

 

15  65.55.42.1 (65.55.42.1)  215.448 ms  215.244 ms  214.590 ms

Any help would be greatly appreciated

Staff
39,779 Points
2015-07-20 4:41 pm
Hello Travis,

The latency starts at hop 6, which is at an IP owned by equinix.com. The network name is ae12-0.ch1-96c-2a.ntwk.msn.net which seems to indicate it is a Microsoft network. Hope this helps!

Kindest Regards,
Scott M
n/a Points
2015-07-20 10:31 am

I tested the speed from the Optimum Online - 52 ms pingdwnld 10.04upld 4.79Should I get a higher speed?

Staff
39,779 Points
2015-07-20 4:42 pm
Hello Carolina,
I am not sure what you are asking. Could you be a bit more specific?

Kindest Regards,
Scott M
n/a Points
2015-07-21 10:14 am

52 ms ping download

10.04 upload

 4.79 download

Should I get an increase to get higher speed?

Staff
10,077 Points
2015-07-21 11:51 pm
Hello Carolina,

That speed looks fine to me, can you explain more in detail what this pertains to such as FTP connections?

Best Regards,
TJ Edens
n/a Points
2015-09-13 2:02 pm

Doing a traceroute how would i know if my ISP is blocking ICMP packets??

Staff
39,779 Points
2015-09-14 1:28 pm
Hello Mark,

Doing a traceroute I don't believe there is a way to tell 100% if a specific hop (ISP, router, etc) is blocking ICMP. You may just try to ask your ISP support directly to be certain.

Kindest Regards,
Scott M
n/a Points
2015-10-05 4:00 am

  1    <1 ms    <1 ms    <1 ms  192.168.1.1  2    23 ms    23 ms    24 ms  175.137.109.94  3     *        *        *     Request timed out.  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. 11     *        *        *     Request timed out. 12     *        *        *     Request timed out. 13     *        *        *     Request timed out. 14     *        *        *     Request timed out. 15     *        *        *     Request timed out. 16     *        *        *     Request timed out. 17     *        *        *     Request timed out. 18     *        *        *     Request timed out. 19     *        *        *     Request timed out. 20     *        *        *     Request timed out. 21     *        *        *     Request timed out. 22     *        *        *     Request timed out. 23     *        *        *     Request timed out. 24     *        *        *     Request timed out. 25     *        *        *     Request timed out. 26     *        *        *     Request timed out. 27     *        *        *     Request timed out. 28     *        *        *     Request timed out. 29     *        *        *     Request timed out. 30     *        *        *     Request timed out.Trace complete.IT IS OK ?

Staff
39,779 Points
2015-10-05 12:54 pm
Hello Stiles,

The trace shows that the connection never got past the second hop. Tracing that IP, it is in Malaysia, Pulau Pinang, George Town.

Kindest Regards,
Scott M
n/a Points
2015-10-08 4:54 pm

Hey Guysso i did the trace tooand in my 4 and 5 hop it just said requested timed out

and stars where the 3 numbers should beI run the trace for www.google.com

Staff
25,021 Points
2015-10-08 5:18 pm
Hello Atom,

Thank you for contacting us. A "request time out" message can indicate an issue with the router/switch, or a switch set to not.

Performing a Ping & Traceroute may provide additional clues on your connection.

Thank you,
John-Paul
n/a Points
2015-10-09 7:09 pm

What happens if you run it and it shows all * from the begining to the end?  If I understand it correctly, this means you're blocked from running certain network tools, but who or what is blocking it?  Firewall or router?  How can I tell?  Details would be great.  Thanks!

Staff
39,779 Points
2015-10-09 7:28 pm
Hello Hanna,

Do you even get a first hop?

Kindest Regards,
Scott M
n/a Points
2015-10-12 12:04 am

No, it is all *.  What does this mean?  And what does it mean if I do get a first hop (in case I was mis-remembering). 

Staff
39,779 Points
2015-10-12 7:55 am
Hello Hanna,

If you are not even getting a first hop then it likely means an issue with your local machine or network. You will need to start looking (or have someone look) there.

Kindest Regards,
Scott M
n/a Points
2015-10-13 2:10 pm

Hi Scott, what if I got a first hop, but the second hop onwards is showing all ***?

Staff
10,077 Points
2015-10-13 3:51 pm
Hello Hanna,

That means that the request is timing out as soon as it leaves your router/modem. You may need to contact your ISP in order to have the issue resolved or investigated further.

Best Regards,
TJ Edens
n/a Points
2015-10-13 6:26 pm

Thanks, TJ.  I thought I had read somewhere that typically it means my firewall or whatever is blocking the request. 

2015-10-10 6:10 am
Hello everyone,
I've been suddenly having an issue with my connection which started three weeks ago. My ping has been spiking to 100~300ms and 500~1000ms whenever I play a game such as League of Legends. It is normally around 50~70ms in ping tests and games.

This is a tracert I just took on LAN (Ethernet)
http://puu.sh/kEZ85/4866a8bd99.png

This is a ping test I also took on LAN (Ethernet).
http://puu.sh/kEVn2/41fe271063.png

I normally use my laptop for gaming on WiFi, but I decided to conduct tests using my desktop which is LAN connected.

Does anyone know what my problem might be?
Staff
39,779 Points
2015-10-12 8:34 am
Hello Fi,

It seems your latency starts around the third hop. That is usually either your router or your first ISP node. You may want to check with your ISP to see if they can assist you.

Kindest Regards,
Scott M
n/a Points
2015-10-23 6:54 am

Can anyone help in understanding me this tracert result.

my wesbite goes down for 5 mibutes 4 times a day.

C:\Users\Rocky>tracert mywesbite.com

 

Tracing route to mywebsite.com [103.21.58.155]

over a maximum of 30 hops:

 

  1     2 ms     2 ms     3 ms  192.168.1.1

  2    28 ms    28 ms    34 ms  abts-north-static-073.220.160.122.airtelbroadban

d.in [122.160.220.73]

  3     *        *        *     Request timed out.

  4    86 ms    90 ms    89 ms  abts-north-static-121.176.144.59.airtelbroadband

.in [59.144.176.121]

  5   179 ms   153 ms   153 ms  182.79.255.106

  6   189 ms   187 ms   188 ms  202.56.223.138

  7   143 ms   139 ms    72 ms  182.79.224.21

  8   191 ms   179 ms   168 ms  182.79.245.161

  9   168 ms   168 ms   168 ms  213.242.116.157

 10     *        *        *     Request timed out.

 11   226 ms   206 ms   207 ms  213.19.196.170

 12   232 ms   233 ms   232 ms  5.100.158.1

 13     *        *        *     Request timed out.

 14   209 ms   209 ms   208 ms  md-in-6.webhostbox.net [103.21.58.155]

 

Trace complete.

 

 

Staff
10,077 Points
2015-10-26 11:37 am
Hello kunal taneja,

I do not think your website is going down but the server location is so far away from you, almost across seas it seems. Have you contacted your host to check to see if your website was going down?

Best Regards,
TJ Edens
n/a Points
2015-10-25 7:26 am

Hello Scott, 

 

Please help me. I need your help badly. I've been having problems with my ISP for the past 3 weeks now and I'm not seeing rainbow on its 4th week. 

 

They said they've already checked and fixed their network/base station where I am connected and even replaced my modem/router and canopy. I'm using a wireless connection with a 5Mbps plan. 

 

I ran ping test on google and facebook, and got high latency, in as much as 2000ms last week and around 400-500ms this week. I also ran trace route but I can't fully identify the figures I am getting. The only thing common that I see is that the numbers 3 and 6 lines are both coming up as request timed out, this applies to all the sites I've ran it with. 

 

Kindly check the sample trace route for google: 

 

1      3ms    10ms   <1ms

2      2ms    2ms       1ms

3      *        *            *       ---- request timed out

4      76ms  78ms      65ms

5      87ms  67ms      *

6      *        *            *       ---- request timed out

7      74ms  59ms      62ms

8      96ms  *            110ms

9      47ms  57ms      58ms

10    81ms  62ms      94ms

11    94ms  75ms      69ms

 

Also, if I may add, the current situation is that, we can't access facebook, it tries to load for a few minutes, but won't display anything, it's just the blue facebook top, with my profile but nothing else. The only trime I can access facebook will be around 1AM till roughly 10PM. This goes the same with the sites where I work. However, youtube loads fine. And one thing I noticed, the upload speed is way better than the download. It is very intermittent. 

Any help will be appreciated. Thank you. 

Staff
39,779 Points
2015-10-26 2:05 pm
Hello Joan,

Your trace report looks fine, at least in this instance. The times are all good. Don't worry about occasional 'time outs' if the numbers look good, those routers could be set to not report.

I had a similar issue recently that got worse until I could not bring up any site. I checked other devices on my network like my phone, other computers, etc and they were fine. That pointed to the specific computer. It turned out to be my wireless network adapter.

I am in no way saying that is your issue, but try to rule out or confirm it is a network issue by using other devices if you can. If other devices behave similarly, you know it is not the computer. If the other devices work fine, then you may want to look at the specific machine for the issue.

Kindest Regards,
Scott M
n/a Points
2015-10-27 1:34 am

Thank you for your feedback. 

Here are the things we did so far. 

Since their technician replaced the modem/router and canopy, I also asked them to bring their own laptop to check the connection with. It yielded to the same results. No matter what we use, 2 laptops, 2 mobile phones, 1 tab and we're getting the same problem. We can only access facebook mostly around 1AM till 12Noon max and my work sites can only be accessed mostly during weekdays. However, when we use other connections, the websites and facebook open up fine. We have also tried running ipconfig /release and /renew, we also tried to change the DNS settings, speedtest is also erratic, though with a 5Mbs subscriptions, sometimes we get as high as 18Mbps and as low as 0.2 Mbps, though getting the same results in terms of browsing. 

Also, the trace routes came up with the same request timed out on lines 3 and 6, no matter what website you try it with. 

 

n/a Points
2015-11-29 8:33 pm

how would i know if the passed hops is a router or not if it is connected to my ISP or to my network?

Staff
39,779 Points
2015-11-30 6:36 pm
Hello Ian,

You would need to check the IP to see who owns it. There are websites such as ip2location which can do that for you

Kindest Regards,
Scott M
n/a Points
2015-12-04 4:08 pm

some one help me get configuration file currently working in kenya via safaricom.com ISP provider. they recently closed that of 196.201.216.13

Staff
34,772 Points
2015-12-04 4:34 pm
Hello Charles,

Sorry for the problem with the ISP and the closed IP address. Unfortunately, we have no way to fix the IP address if it's been blocked from you. You should contact your ISP for assistance with this issue. If you're trying to resolve another issue please provide us with more information.

Kindest regards,
Arnel C.
n/a Points
2015-12-06 11:11 pm

Complete technical noob here so I have a really simple question I'm hoping I can get some help with. 

 

I've run the traceroute several times and I understand what most of the output means.  I understand there are three columns for each row which are supposed to help show an average of the time.  However when I run the report I almost always have an extreme outlier among the three.  I've been having major issues with my internet (mostly console gaming or streaming) and I'm wondering if that could be the sign of an underlying problem. 

Thanks in advance for any help! 

Here is an example: 

 

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
 
C:\Users\Ryan>tracert google.com
 
Tracing route to google.com [216.58.216.78]
over a maximum of 30 hops:
 
  1     2 ms    <1 ms    <1 ms  192.168.1.1
  2    34 ms   319 ms    80 ms  96.120.112.129
  3    17 ms    13 ms    28 ms  te-0-0-0-7-sur03.noblesville.in.indiana.comcast.
net [69.139.232.205]
  4    26 ms    17 ms    16 ms  69.139.202.213
  5    24 ms    94 ms   342 ms  he-4-9-0-0-ar01.area4.il.chicago.comcast.net [68
.85.177.121]
  6    37 ms    35 ms   299 ms  be-33491-cr02.350ecermak.il.ibone.comcast.net [6
8.86.91.165]
  7    72 ms    74 ms    35 ms  68.86.88.230
  8   135 ms    52 ms    54 ms  as15169-4-c.350ecermak.il.ibone.comcast.net [173
.167.57.222]
  9   286 ms   100 ms    34 ms  209.85.143.184
 10   205 ms    55 ms    45 ms  72.14.237.231
 11    44 ms    59 ms    83 ms  ord30s21-in-f14.1e100.net [216.58.216.78]
 
Trace complete.
 
 
Staff
39,779 Points
2015-12-07 4:19 pm
Hello Ryan,

In looking at the trace, there does not seem to be an issue. It is not uncommon to have an outlier that seems to spike. As long as it does not continue to increase in the hops afterwards, it is not an issue. Sadly, your trace does not show anything that I could identify as a cause for latency.


Kindest Regards,
Scott M
n/a Points
2015-12-16 12:49 pm

Do you know what is causing three hops to time out just before reaching inmotion's servers?  I have domains hosted with other companies, and none of them time out anwhere... but my inmotion hosted sites have this three-hop time out... Any insight would be greatly appreciated.

 

 1  router.belkin (192.168.2.1)  1.445 ms  1.404 ms  0.849 ms

 2  10.1.10.1 (10.1.10.1)  1.711 ms  1.662 ms  1.600 ms

 3  96.120.101.137 (96.120.101.137)  15.819 ms  9.613 ms  9.807 ms

 4  te-0-4-0-19-sur03.seattle.wa.seattle.comcast.net (68.86.113.37)  12.773 ms  19.119 ms  11.465 ms

 5  be-20-ar01.seattle.wa.seattle.comcast.net (69.139.164.129)  12.583 ms  13.384 ms  14.402 ms

 6  4.68.71.73 (4.68.71.73)  11.960 ms  11.800 ms  12.148 ms

 7  ae-3-80.edge3.losangeles1.level3.net (4.69.144.137)  39.483 ms  39.869 ms  39.473 ms

 8  ae-2-70.edge3.losangeles1.level3.net (4.69.144.73)  38.488 ms

    ae-1-60.edge3.losangeles1.level3.net (4.69.144.9)  39.409 ms

    ae-2-70.edge3.losangeles1.level3.net (4.69.144.73)  39.616 ms

 9  cr1.lax1.us.packetexchange.net (4.71.136.2)  37.819 ms  48.902 ms  48.204 ms

10  * * *

11  * * *

12  * * *

 

13  biz104.inmotionhosting.com (23.235.208.127)  38.666 ms  45.558 ms  34.925 ms

Staff
34,772 Points
2015-12-16 2:14 pm
Hello Mike D.,

Sorry for the confusion with the traceroute response. The timeouts are not necessarily a bad thing. They may simply be routers that are set to not respond. The end times are really good, so actually, your traceroute indicates that everything's okay. If things were not okay, then you would not have hit the destination or the times would be much, much higher.

I hope this helps to answer your question, please let us know if you require any further assistance.

Regards,
Arnel C.
n/a Points
2015-12-30 11:22 am

This was a great explanation, thanks.  Am currently battling against an increasing latency from 3 hops from the end of my route destination, going from home to my Shoutcast streaming server, different continents, this is going on for a few weeks now.  Is there no way to alter what route my packets take ?  Could rebooting my router change the route ?  I won't reboot my router unless absolutely necessary as I am running a live web radio station.  The streaming works but am having more regular buffering problems since then, so it's not like it's not working at all

However what i will test is, a trace from my holiday place that I will be visiting tomorrow, to see if it's using a different route (different ISP/different geographical area).

Sorry, I should also add that the high latency am talking about is 124ms and stays at that for the remaining 3 hops, maybe you'll think it's not that high but when using WINMTR, it's showing 100% packet loss and doesn't change. Last weekend I was getting "no response from host" now am getting the host name at least at one of those hops and this caused a half hour down time then it was ok but stays showing 100% loss since then

Any further hints greatly appreciated.

Staff
34,772 Points
2015-12-30 11:52 am
Hello Nathalie,

We're sorry to hear that you're having problems with your ISP (Internet Service Provider). InMotion is a hosting service provider where our primary purpose is hosting websites, so we would depend on an Internet Service Provider like you so that our viewers can get to our servers through the internet. If you look at your traceroute, and you do NOT get to your server, then there would be 100% packet loss - as the request from computer trying to access the data is not getting information back. However, if you're getting some type of response - slow or not - then there some data flowing back and forth - meaning it's not 100% packet loss - at least for some periods of time. To answer your question - no, rebooting your router does not change the route to get to your server. This is determined beyond your router and through your ISP. If there are problems with the latency getting to the hosting service, then you may want to contact your hosting service and provide them the trace routes you are seeing from your location. They may be able to fix that for you by addressing the services connecting to the hosting service to provide connection to the internet. If their services are performing normally, then it may be that you will need to talk with your ISP in order to determine why there is significant latency getting to URL in question.

I hope this helps to answer your question, please let us know if you require any further assistance.

Regards,
Arnel C.
2016-01-01 8:25 am
What did you mean when you said in the article, " if the first hop has high latency that it is at Network level? Do you mean it is the Router or up higher at the ISP level? Can you say what would cause such a high latency in the traceroute that I have posted? Thanks so much!

Tracing route to google.com [173.194.46.105] over a maximum of 30 hops:

1 2121 ms 2149 ms * 216.49.101.80

2 2160 ms 1990 ms * 216.49.101.115

3 2019 ms 2016 ms 2372 ms 208.185.28.137

4 2019 ms 1962 ms 2068 ms 64.125.21.217

5 * 2175 ms 1960 ms 72.14.217.53

6 1896 ms 2108 ms * 209.85.254.128

7 2009 ms 2178 ms 2168 ms 209.85.245.225

8 * 2148 ms 2375 ms 173.194.46.105

Trace complete.
n/a Points
2016-01-02 6:55 pm

The router was bad so I know what caused the high latency now.  Thanks...

n/a Points
2016-01-17 7:17 am

Hi, I am having problem in the 13th hope. 

 1     2 ms     1 ms     1 ms  192.168.0.1

  2     2 ms     1 ms     1 ms  192.168.1.1

  3    43 ms    34 ms    30 ms  triband-del-59.180.127.254.bol.net.in [59.180.127.254]

  4    29 ms    27 ms    28 ms  triband-del-59.179.245.10.bol.net.in [59.179.245.10]

  5   778 ms    28 ms    27 ms  triband-del-59.180.210.206.bol.net.in [59.180.210.206]

  6    28 ms    28 ms    28 ms  125.20.37.17

  7   263 ms   263 ms   263 ms  182.79.222.113

  8   264 ms   264 ms   264 ms  los-brdr-01.inet.qwest.net [63.146.27.21]

  9   285 ms   285 ms   285 ms  phn-edge-08.inet.qwest.net [67.14.40.50]

 10   287 ms   286 ms   286 ms  63-232-81-254.dia.static.qwest.net [63.232.81.254]

 11   309 ms   308 ms   311 ms  ip-184-168-2-254.ip.secureserver.net [184.168.2.254]

 12   309 ms   310 ms   308 ms  ip-184-168-2-254.ip.secureserver.net [184.168.2.254]

 13     *        *        *     Request timed out.

 14   535 ms   407 ms   308 ms  ip-160-153-136-1.ip.secureserver.net [160.153.136.1]

 

Trace complete.

Staff
39,779 Points
2016-01-18 11:29 am
Hello Vishesh Rai,

Thank you for the trace example. Following the article above, you can see where the latency begins to affect your connection. You can search on that IP address to find out where it is located so you know the geographic location of the issue and possibly the company involved.

Kindest Regards,
Scott M
n/a Points
2016-01-22 4:32 am

Thanks Scott for a brilliant article. I am a newbe at this and for the first time properly understand this!

n/a Points
2016-01-23 2:52 pm

Hi, I am having high ping and packet loss within Dota 2.

  1     3 ms     3 ms     3 ms  BThomehub.home [192.168.1.254]

  2   349 ms   329 ms   217 ms  217.47.105.122

  3   195 ms   175 ms   151 ms  217.47.106.193

  4    38 ms    40 ms    38 ms  213.1.69.158

  5   105 ms   136 ms   173 ms  31.55.165.102

  6    37 ms    37 ms    38 ms  31.55.165.43

  7    36 ms    36 ms    42 ms  31.55.165.107

  8   238 ms   206 ms   123 ms  109.159.250.60

  9    83 ms    55 ms    64 ms  109.159.255.147

 10   105 ms   134 ms   113 ms  peer2-xe4-0-1.telehouse.ukcore.bt.net [109.159.252.39]

 11    47 ms    46 ms    43 ms  109.159.253.91

 12   575 ms   428 ms   415 ms  162-254-196-137.valve.net [162.254.196.137]

 13   400 ms   365 ms   370 ms  146.66.154.218

 14     *        *        *     Request timed out.

 15   197 ms   168 ms    67 ms  146.66.152.2

Staff
39,779 Points
2016-01-25 5:55 pm
Hello HBomb,

The trace doesnt look like there is any persistent issue. Check the article above for more details.

Kindest Regards,
Scott M
n/a Points
2016-02-04 11:06 pm

This is the trace output.

C:\Users\ICT_PC>tracert drive.google.com

 

Tracing route to drive.google.com [110.164.10.20]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms     *     10.0.8.1

  2     1 ms    <1 ms    <1 ms  58.181.187.113

  3     3 ms     2 ms     1 ms  202.149.111.185

  4    34 ms    18 ms    30 ms  203.209.64.106

  5     4 ms     3 ms     3 ms  203.209.64.105

  6    23 ms    13 ms    17 ms  203.195.104.94

  7     2 ms     3 ms     3 ms  58.181.253.93

  8     3 ms     3 ms     3 ms  58.181.253.202

  9     3 ms     3 ms     3 ms  TIG-Net31-201.trueintergateway.com [122.144.31.2

01]

 10     3 ms     3 ms     3 ms  TIG-Net31-126.trueintergateway.com [122.144.31.1

26]

 11     5 ms     5 ms     5 ms  218.100.66.42

 12     5 ms     5 ms     4 ms  mx-ll-110.164.1-3.static.3bb.co.th [110.164.1.3]

 

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

 

Trace complete.

 

Could you please help me understanding the trace

 

 

Staff
10,077 Points
2016-02-05 10:18 am
Hello Bharathi,

It seems that you hit the google network just fine. Generally when you see request time outs in the either the nodes are too busy to process your request as trace routes have a very low priority when it comes to processing the request. Also it could be that the nodes are configured to deny trace request as that is normal with secure networks as well.

Best Regards,
TJ Edens
n/a Points
2016-02-09 5:15 am

Microsoft Windows [Version 10.0.10586]

(c) 2016 Microsoft Corporation. All rights reserved.

 

C:\Users\user>tracert 206.127.148.171

 

Tracing route to 206-127-148-171.ncsoft.com [206.127.148.171]

over a maximum of 30 hops:

 

  1    15 ms    13 ms    18 ms  192.168.100.1

  2    10 ms     6 ms     4 ms  89.211.3.14

  3    10 ms    41 ms    11 ms  89.211.3.13

  4    14 ms    17 ms     8 ms  89.211.4.138

  5    18 ms    14 ms    12 ms  89.211.5.5

  6    25 ms    48 ms    28 ms  89.211.2.98

  7   113 ms   115 ms   118 ms  xe-4-2-0.mrs10.ip4.gtt.net [46.33.94.21]

  8   130 ms   138 ms   138 ms  xe-10-2-4.fra61.ip4.gtt.net [89.149.129.186]

  9   221 ms   228 ms   227 ms  cdnetworks-gw.ip4.gtt.net [77.67.71.122]

 10   231 ms   238 ms   238 ms  206-127-157-94.ncsoft.com [206.127.157.94]

 11   238 ms   231 ms   249 ms  206-127-148-171.ncsoft.com [206.127.148.171]

 

Trace complete.

 

is there an issue to my ip? im in wired connection but i start with high ping instead of 1ms 

 

Staff
5,515 Points
2016-02-09 9:53 am
It looks like you are seeing some latency crossing oceans, but otherwise the trace looks good.
n/a Points
2016-02-23 10:21 pm

I'm seeing timeout on the 1st entry, does that mean I'm having internal network related issues?   Can someone shed some light on this one?

Thanks!

 

-AL-

 

 

 

Tracing route to dns136.online.tj.cn [111.161.74.136] over a maximum of 30 hops:

 1     *        *        *     Request timed out. 2     5 ms     6 ms     7 ms  42.61.95.45  3     2 ms     2 ms     2 ms  115.42.140.249 4     2 ms     2 ms     1 ms  115.42.140.250 5     2 ms     2 ms     3 ms  119.75.50.149 6     2 ms     2 ms     2 ms  165.21.12.68  7     2 ms     2 ms     2 ms  203.208.174.33 8     3 ms     3 ms     2 ms  203.208.158.1 9    47 ms    47 ms    47 ms  203.208.171.8110    48 ms    47 ms    47 ms  219.158.96.22111    81 ms    80 ms    79 ms  219.158.23.9 12   240 ms   231 ms   232 ms  219.158.7.1713   264 ms   259 ms   231 ms  219.158.102.58 14     *        *        *     Request timed out.15   123 ms   127 ms   128 ms  61.181.25.49 16     *        *        *     Request timed out.17     *        *        *     Request timed out.18     *        *        *     Request timed out.19     *        *        *     Request timed out.20     *        *        *     Request timed out.21     *        *        *     Request timed out.22     *        *        *     Request timed out.23     *        *        *     Request timed out.24     *        *        *     Request timed out.25     *        *        *     Request timed out.26     *        *        *     Request timed out.27     *        *        *     Request timed out.28     *        *        *     Request timed out.29     *        *        *     Request timed out.30     *        *        *     Request timed out.

Trace complete.

Staff
34,772 Points
2016-02-24 4:57 pm
Hello Al,

As per our tutorial above, a timeout or two in the beginning of the traceroute is generally not a problem. There may be something simply not responding which is normal at the beginning of the trace.

If you have any further questions or comments, please let us know.

Regards,
Arnel C.
n/a Points
2016-02-27 1:11 am

I'm having an awful time getting my site to come up on my desktop. The mobile version comes up though. My internet provider and hosting company are pointing fingers at each other. So i'm trying to decide if i need to change hosting to you all - which would be a big shift for us. Could you look at this traceroute and tell me anything? my hosting company wants me to call level3.net and ask why i can't see the site. I don't even work with them? Why would i call a third party about my issue?

 

--- ping statistics ---

12 packets transmitted, 11 packets received, 8.3% packet loss

round-trip min/avg/max/stddev = 52.858/71.532/127.349/24.091 ms

traceroute

traceroute to  (184.168.47.225), 64 hops max, 52 byte packets

 1  10.0.0.1 (10.0.0.1)  5.416 ms  5.402 ms  4.532 ms

 2  96.120.13.73 (96.120.13.73)  14.947 ms  12.272 ms  13.557 ms

 3  xe-10-0-1-sur03.littleton.co.denver.comcast.net (68.85.220.89)  13.405 ms  14.025 ms  15.455 ms

 4  ae-22-ar01.denver.co.denver.comcast.net (68.86.179.237)  14.624 ms  18.132 ms  16.282 ms

 5  4.68.63.165 (4.68.63.165)  20.321 ms  14.650 ms  13.780 ms

 6  ae-1-8.bar1.phoenix1.level3.net (4.69.133.29)  80.695 ms  142.068 ms  55.941 ms

 7  4.16.137.146 (4.16.137.146)  60.347 ms  54.397 ms  50.577 ms

 8  * * *

 9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

 

17  * * *

Staff
39,779 Points
2016-02-29 3:18 pm
Hello Liz,

The traceroute you provided shows a definite problem at the 7th hop. From that point on, the signal is not getting through. The IP address there shows that the router with the problem is owned by Level3. They are a backbone company, think of them as an interstate highway, but the interNET version.

Although you CAN contact Level 3 regarding your situation, it may be better to check and see if your ISP is having an issue with Level 3, or check to see if the hosting company is having an issue with them. Since Level 3 is closer to the hosting company in the trace, I would have them check first. It could possibly also be a firewall issue at the datacenter if Level 3 is feeding traffic to it. In cases like that, the majority of traffic can be fine, but for some reason your IP address may be blocked there. In that case, the hosting company may be able to get you unblocked.

Sorry to hear you are having issues, but I hope it all gets worked out for you!

Kindest Regards,
Scott M
n/a Points
2016-03-01 1:59 pm

thank you! I really appreciate you taking the time to answer my comment. I figured out the issue - we had a bunch of old A records and AAAA records from previous developers that had worked on the site - and they hadn't deleted unused ones. Note sure why we would ever need those. I will consider Inmotion in the future for hosting. Thank you!!! 

n/a Points
2016-03-11 7:48 am

I am not fully satisfied with the last statement in the article i.e.

If it is anywhere prior to that, the issue is simply along the route and is within neither your nor your hosting provider's control.

i think we can call that person responsible for  that ip causing problem by know there location. any comment please

Staff
39,779 Points
2016-03-28 1:52 pm
If you can identify an IP along the route that is having an issue, then yes, that router and its owner would be the cause. They would be responsible for fixing the issue on their side. This can often happen where it is neither the user nor the provider.
n/a Points
2016-03-30 12:14 am

very very useful article,i have one question why dies it show time out when it reach a fire wall

Staff
34,772 Points
2016-03-30 5:00 pm
Hello Sarath,

Firewalls don't necessarily provide the information requested by the traceroute. This is stated above: "The target's firewall may be blocking requests. The target is still most probably reachable with a normal HTTP request, however. This should not affect normal connection".

So although the connection is made, there is no information provided to the traceroute.

If you have any further questions or comments, please let us know.

Regards,
Arnel C.
n/a Points
2016-04-01 1:31 am

very  useful article

n/a Points
2016-04-25 11:49 pm

Can you please help me understand this result? I was referred back to the internet provider.

 

 1  dsldevice (10.0.0.138)  0.755 ms  0.543 ms  0.558 ms 2  * * * 3  144.130.213.210 (144.130.213.210)  19.827 ms  19.323 ms  19.895 ms 4  bundle-ether7.cha-core4.brisbane.telstra.net (203.50.11.142)  21.969 ms  21.577 ms  19.406 ms 5  bundle-ether11.ken-core10.sydney.telstra.net (203.50.11.72)  42.166 ms  38.029 ms  40.447 ms 6  bundle-ether1.ken-edge902.sydney.telstra.net (203.50.11.97)  36.322 ms  41.611 ms  36.850 ms 7  voc1765203.lnk.telstra.net (139.130.196.238)  38.665 ms  42.025 ms  40.207 ms 8  ip-130.28.92.203.vocus.net.au (49.255.234.130)  36.337 ms  35.967 ms  36.371 ms 9  s-br1-glbl-1.pr1.prth.nxg.net.au (150.207.242.71)  84.313 ms  83.962 ms  83.998 ms10  * * * 11  * * *12  * * *13  * * *14  * * *15  * * *16  * * *17  * * *18  * * *19  * * *20  * * *21  * * *22  * * *23  * * *24  * * *25  * * *26  * * *27  * * *28  * * *

Staff
5,515 Points
2016-04-26 7:19 am
The signal seems to time out after reaching 150.207.242.71. There could be many reasons for this. I'll refer you to the section of the above article headed "Timeouts at the very end of the report" for a list of possible causes.
n/a Points
2016-05-07 3:06 pm

Can you please help me understand my result? Here are my results:

  1     1 ms    <1 ms    <1 ms  den [192.168.2.1]

  2    10 ms    17 ms     8 ms  10.72.64.1

  3     8 ms     9 ms     9 ms  ten4-0-1.bkfd01-ser1.bhn.net [72.31.201.150]

  4    10 ms    10 ms     9 ms  72-31-201-166.net.bhntampa.com [72.31.201.166]

  5    10 ms     9 ms     9 ms  ten0-2-0-0.bkfd01-car2.bhn.net [72.31.200.181]

  6    22 ms    17 ms    16 ms  10.bu-ether18.tustca4200w-bcr00.tbone.rr.com [107.14.16.236]

  7    21 ms    15 ms    18 ms  agg5.tustcaft01r.socal.rr.com [66.109.1.219]

  8    16 ms    20 ms    18 ms  216.156.65.225.ptr.us.xo.net [216.156.65.225]

  9    68 ms    69 ms    68 ms  207.88.14.212.ptr.us.xo.net [207.88.14.212]

 10    92 ms    70 ms    81 ms  207.88.12.131.ptr.us.xo.net [207.88.12.131]

 11    74 ms    75 ms    71 ms  207.88.12.152.ptr.us.xo.net [207.88.12.152]

 12    69 ms    69 ms    73 ms  207.88.12.178.ptr.us.xo.net [207.88.12.178]

 13    69 ms    67 ms    77 ms  te-3-4-0.rar3.sanjose-ca.us.xo.net [207.88.12.177]

 14    70 ms    69 ms    70 ms  cir1.atlanta6-ga.us.xo.net [207.88.13.49]

 15    82 ms    80 ms    92 ms  216.156.108.18.ptr.us.xo.net [216.156.108.18]

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

 

Trace complete.

 

Staff
39,779 Points
2016-05-09 11:21 am
If you hit timeouts and they never respond afterwards, then the last IP on the list is the problem. In your case, that router is owned by XO Communications in Atlanta, Georgia, USA. They are the ones that will correct the issue.
n/a Points
2016-05-17 11:16 am

I have this problem with all of my inmotionhosting domains... and only my inmotionhosting domains.  They timeout close to the end.  I have sites hosted with 4 different companies, and only yours seem to timeout close to the host.  I've looked into this many times, and never been able to get a good explanation.  Any insight would be helpful:

 

 1  router.belkin (192.168.2.1)  2.979 ms  0.940 ms  1.218 ms

 2  10.1.10.1 (10.1.10.1)  1.954 ms  1.601 ms  1.520 ms

 3  96.120.102.45 (96.120.102.45)  15.344 ms  10.858 ms  9.831 ms

 4  te-0-0-0-21-sur02.seattle.wa.seattle.comcast.net (96.108.136.133)  10.291 ms  16.010 ms  10.616 ms

 5  be-20-ar01.burien.wa.seattle.comcast.net (69.139.164.125)  10.244 ms  14.198 ms  9.428 ms

 6  4.68.71.77 (4.68.71.77)  14.018 ms  9.324 ms  10.122 ms

 7  * * *

 8  cr1.lax1.us.packetexchange.net (4.71.136.2)  36.448 ms  48.110 ms  35.999 ms

 9  * * *

10  * * *

11  * * *

 

12  ld145.inmotionhosting.com (23.235.210.210)  36.037 ms  33.756 ms  37.425 ms

Staff
5,515 Points
2016-05-17 6:38 pm
I refer you to the article above, particularly the section headed "High latency in the middle but not at beginning or end". Basically, these indicate a long hop and do not necessarily indicate an issue.
n/a Points
2016-05-26 12:39 am

Hello. :) I was trying to access www.****.org but says "this site cant be reached". So, I performed tracert command to check.

With this traceroute result, who I should call to have the issue resolved for me. I believe its the hosting company that hosts pnpmisorppo website. Please correct me if I'm wrong. I can't even reach the website's Cpanel.

1   2ms   1ms   1ms   192.168.22.1

2   3ms   6ms   3ms   192.168.15.1

3   * * *

4   * * *

5   52ms  70ms 3ms   10.169.43.77

6   * * *

7   * * 83ms   122.2.175.149.static.pldt.net [122.2.175.149]

8   * * *

9   * * *

10 * * *

11 * * *

12 *262ms  265ms   ae2.bbr02.eq01.sjc02.networklayer.com

13 * * 207ms ae0.bbr02.cs01.lax01.networklayer.com

14 220ms   223ms   230ms   ae7.bbr01.cs01.lax01.networklayer.com

15  312ms   *   278ms   173.192.18.149

16 * * *

up to

30 * * *

Staff
25,021 Points
2016-05-26 12:16 pm
Hello,

Thank you for contacting us. With so many unresponsive hops indicated by asterisks "* * *" it is difficult to narrow down, but you may want to contact your ISP first to see if there are known issues.

Also, you may want to perform the Ping/Traceroute again to see if it gets a similar result. As it may have been a momentary issue.

Are you getting packet loss on the ping?

Thank you,
John-Paul
n/a Points
2016-06-12 8:07 pm

Tracing route to www.google.com [2607:f8b0:4005:804::2004]

over a maximum of 30 hops:

 

  1     9 ms     9 ms     7 ms  2605:e000:bfc0:68::1

  2     8 ms     7 ms     8 ms  2605:e000:bfc0:68::1

  3    10 ms     9 ms    10 ms  2605:e000:0:4::3:589

  4    12 ms    18 ms    10 ms  2605:e000:0:4::3:6d0

  5     *        *        *     Request timed out.

  6    11 ms     *        *     2610:18:114:8::1

  7    12 ms    10 ms    10 ms  2610:18:114:8::1

  8    11 ms    10 ms    10 ms  2610:18:114:c::2

  9     *       12 ms    10 ms  2001:4860::1:0:c432

 10     *       10 ms    11 ms  2001:4860::8:0:7a19

 11    22 ms    22 ms    21 ms  2001:4860::8:0:8bb4

 12    22 ms    22 ms    23 ms  2001:4860::1:0:ae01

 13    21 ms    20 ms    23 ms  2001:4860:0:1::1b8b

 14     *       20 ms    20 ms  sfo07s13-in-x04.1e100.net [2607:f8b0:4005:804::2004]

any idea for a solution? happens during my gaming as well where it just drops momentarily. im hardwired. 

Staff
39,779 Points
2016-06-13 2:33 pm
That traceroute looks very good. There is nothing there to show any issues.
n/a Points
2016-07-14 5:10 am

I am specifically having problems with opening economist.com so I tried a tracert to see what is wrong. The results are shared by me below - 

 

tracert www.economist.com

 

Tracing route to e2svi.x.incapdns.net [103.28.249.108]

over a maximum of 30 hops:

 

  1     1 ms     1 ms     1 ms  edimax.setup [192.168.2.1]

  2     3 ms     2 ms     2 ms  190-73-5-110.mysipl.com [110.5.73.190]

  3    10 ms     *        *     189-73-5-110.mysipl.com [110.5.73.189]

  4    54 ms    53 ms    54 ms  9-97-87-183.mysipl.com [183.87.97.9]

  5    89 ms    92 ms    99 ms  182.79.208.18

  6    96 ms   101 ms    93 ms  202.56.223.193

  7    39 ms    29 ms    34 ms  182.79.220.206

  8   115 ms    95 ms    95 ms  182.79.245.201

  9    95 ms    97 ms    94 ms  203.131.246.29

 10   104 ms    95 ms   126 ms  ae-6.r22.tkokhk01.hk.bb.gin.ntt.net [129.250.4.6]

 11   151 ms   139 ms   139 ms  ae-16.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.5.133]

 12     *      140 ms   139 ms  ae-10.r27.tokyjp05.jp.bb.gin.ntt.net [129.250.2.156]

 13   146 ms   139 ms   145 ms  61.213.179.194

 14   241 ms   139 ms   139 ms  103.28.249.108.ip.incapdns.net [103.28.249.108]

 

Can you help me to find the problem and provide a solution?

Staff
11,563 Points
2016-07-14 9:21 am
There is a bit of latency in your hops around hop 10. This may be causing issues for your connection to the website. Other than that, I'd suggest reaching out to your ISP. Typically, these issues resolve themselves pretty quickly on their own.
n/a Points
2016-07-15 7:02 pm

My Trace Route seems to go to an island off of Africa before returning to Puerto Rico on any trace. Wondering why?  Milliseconds matter to me.

#CountryTownLatLonIPHostnameLatency (ms)DNS Lookup (ms)Distance to previous node (km)Whois

1Puerto RicoSan Juan18.420807-66.0616192.168.0.1(None)16310192.168.0.1

2(Unknown)(Unknown)0.00.010.240.160.1(None)3146749810.240.160.1

3(Unknown)(Unknown)0.00.010.65.2.66(None)3247010.65.2.66

4(Unknown)(Unknown)0.00.010.65.1.122(None)3132010.65.1.122

5Puerto Rico(Unknown)18.25-66.563.245.22.37xe-8-2-0.usa.pr-edge02.columbus-networks.com1631754163.245.22.37

6United StatesMiami25.927399-80.180163.245.5.62xe-0-0-2.usa.brx-teracore01.columbus-networks.com4631164763.245.5.62

7United StatesMiami25.927399-80.180163.245.6.182(None)4747063.245.6.182

8United StatesMountain View37.419205-122.0574209.85.241.96(None)621094130209.85.241.96

9United StatesMountain View37.419205-122.057472.14.233.89(None)62125072.14.233.89

10United StatesMountain View37.419205-122.0574216.58.192.78mia07s34-in-f78.1e100.net47160216.58.192.78

Thanks

 

Staff
25,021 Points
2016-07-18 10:11 am
It is difficult to troubleshoot without the timestamps included. If you suspect a poorly routed connection, I recommend contacting your ISP (Internet Service Provider) with your full ping and traceroute as evidence of the issue.

Thank you,
John-Paul
2016-07-26 11:49 am
I've noticed recently that my access to Google, Yahoo and a few other sites has slowed down considerably. We've had this same ISP for several years, but never had the connection slow down like this before.

I tried a traceroute to Google and this is the result I got:

1 1 ms 2 ms 1 ms 192.168.10.1
2 580 ms 26 ms 21 ms nurkla1.fi.elisa.net [91.154.208.1]
3 20 ms 20 ms 20 ms 139.97.102.104
4 18 ms 19 ms 19 ms ip-rr.hkika234.fi.elisa.net [139.97.0.162]
5 21 ms 19 ms 19 ms 139.97.94.55
6 21 ms 19 ms 19 ms 213.192.186.77
7 26 ms 25 ms 25 ms 213.192.184.74
8 25 ms 25 ms 25 ms 74.125.50.145
9 50 ms 57 ms 50 ms 216.239.43.122
10 50 ms 50 ms 50 ms 108.170.235.63
11 50 ms 49 ms 49 ms arn09s10-in-f4.1e100.net [216.58.211.132]

...That huge spike doesn't look normal...
Staff
5,515 Points
2016-07-26 12:35 pm
It looks like the IP on the first hop belongs to Elisa Hostmaster. I suppose they are your ISP. I advise contacting them and providing this trace route for their reference.
n/a Points
2016-07-29 10:14 am

Can you please tran dhelp me identify the problem with the below trace ?

 

Tracing route to 10.25.17.156 over a maximum of 30 hops

 

  1    <1 ms    <1 ms    <1 ms  10.80.8.10

  2     *        *        *     Request timed out.

  3    <1 ms    <1 ms    <1 ms  10.80.8.2

  4     9 ms     9 ms     9 ms  162.97.93.221

  5     9 ms     9 ms     9 ms  100.65.0.5

  6    10 ms    10 ms    10 ms  100.65.0.6

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

Staff
34,772 Points
2016-07-29 11:17 am
Hello Waheda,

The traceroute is dead-ending in an unknown location in your traceroute. There may have been a temporary problem with the route. Try running the trace again. If you continue to get the same result, then copy the traceroute results and send them to our live technical support department in a verified ticket. They will be able to look at it and recommend if the issue belongs with your ISP, or if it's something that we can resolve ourselves.

If you have any further questions or comments, please let us know.

Regards,
Arnel C.
n/a Points
2016-08-01 5:27 am

Thank you for your help Arn. 

I have tried it again and the problem seems to persist. As suggested, i have sent the trace request to your IT support team.

 

Regards,

waheda

n/a Points
2016-08-03 11:07 am

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

.110]

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11   314 ms   469 ms   559 ms  eccomp12-havp2.inmotionhosting.com [104.193.140.

14]

 12   607 ms   480 ms   319 ms  vps19236.inmotionhosting.com [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>

Staff
34,772 Points
2016-08-03 4:49 pm
Hello Nuwan,

Sorry for the problems with connecting to the server. Looking at that traceroute you can see that early on you are getting triple digits through the networks you're going through to get to the server. It is possible that the problems with the routing are temporary. However, if you consistently see the same problem over several days, then you should submit a verified support ticket with your complete traceroute and description of the issue. Early issues in the routing are typically related to your ISP.

If you have any further questions or comments, please let us know.

Regards,
Arnel C.
n/a Points
2016-09-01 12:19 pm

For the past week and a half, I've been having issues with the livestreaming website Twitch.  I live in Puerto Rico and my ISP speed is 40 mbps down and 4 mbps up.  I have absolutely zero problems connecting with any other website, online gaming or watching other streaming services in HD quality.  I used to be able to watch Twitch on source or high quality and now I can't even watch it on low, doesn't matter if it's on the PC, my Xbox or my iPad.

I did the traceroute and after hop #10, the latency went up the 100s but stayed below the 170s.

After hop #20, the requests just timed out and it never got to it's destination.

C:\Users\Ricardo>tracert twitch.tv

Tracing route to twitch.tv [50.112.196.159]

over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]

  2    <1 ms    <1 ms    <1 ms  192.168.0.1

  3    23 ms    10 ms     9 ms  10.240.32.1

  4     9 ms     9 ms    14 ms  10.65.2.18

  5    10 ms    13 ms    14 ms  10.65.1.122

  6    46 ms    49 ms    55 ms  63.245.23.169

  7    48 ms    54 ms    47 ms  63.245.5.230

  8    52 ms    47 ms    50 ms  mai-b1-link.telia.net [213.248.86.85]

  9    71 ms    71 ms    71 ms  atl-b22-link.telia.net [62.115.143.102]

 10    79 ms    78 ms    79 ms  chi-b21-link.telia.net [62.115.116.125]

 11   122 ms   128 ms   124 ms  sea-b1-link.telia.net [62.115.117.48]

 12   127 ms   131 ms   126 ms  amazon-ic-302506-sea-b1.c.telia.net [213.248.84.

190]

 13   147 ms   122 ms   131 ms  52.95.52.248

 14   127 ms   127 ms   127 ms  52.95.53.7

 15   129 ms   131 ms   131 ms  54.239.41.248

 16   167 ms   147 ms   162 ms  52.93.12.42

 17   129 ms   132 ms   131 ms  52.93.12.33

 18   161 ms   160 ms   172 ms  52.93.12.104

 19   134 ms   133 ms   130 ms  52.93.12.129

 20   133 ms   129 ms   148 ms  205.251.232.63

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Ricardo>ping twitch.tv

Pinging twitch.tv [50.112.196.159] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 50.112.196.159:

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

 

Is there anything I can do or contact my ISP and show them this data?  I'm sorry for the lenghty post.

I appreciate your time.

Thank you!

Staff
25,021 Points
2016-09-01 3:00 pm
Yes, I think it would be beneficial to contact your ISP with this information. Especially since you are experiencing 100% loss.

Thank you,
John-Paul

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.

110 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!