Jump to content

Tracert'ing!


FiberOptic

Recommended Posts

Well.. I have seen alot of people post tracerts to google.com,.

However, Their first ones be anything from 1-5 why are mine soo high? Could this be the problem with my speeds?

Microsoft Windows [Version 6.0.6000]

Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:UsersAquib Hussain>tracert google.com

Tracing route to google.com [64.233.187.99]

over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  192.168.0.1

  2    56 ms    39 ms    53 ms  cr0.wmrj.uk.easynet.net [195.189.159.54]

  3    22 ms    23 ms    22 ms  80.238.50.65

  4     *       29 ms    30 ms  ip-89-200-132-80.ov.easynet.net [89.200.132.80]

  5    29 ms    28 ms    28 ms  ge2-1-0.er3.tclon.uk.easynet.net [89.200.130.0]

  6    29 ms    28 ms    31 ms  195.66.226.125

  7    29 ms    29 ms    29 ms  66.249.95.130

  8    98 ms    97 ms    97 ms  72.14.236.216

  9   103 ms   102 ms   102 ms  66.249.94.235

10   116 ms   115 ms   115 ms  72.14.238.138

11   117 ms   117 ms   117 ms  72.14.236.19

12   120 ms   120 ms   124 ms  216.239.49.222

13   117 ms   117 ms   117 ms  jc-in-f99.google.com [64.233.187.99]

Trace complete.

C:UsersAquib Hussain>

Link to comment
Share on other sites

that isnt good for a first hop that is for sure.. it could be a problem for your speed.. looks like you are dropping packets at the third router.. that is what the * indicates..  Which means you are having to resend the information..

Link to comment
Share on other sites

that isn't what he means... the internet runs off of many routers/switches.. he is saying that on the 3rd router that you pass by.. its having problems transfering data..which is giving you packetloss..

C:UsersTim>tracert google.com

Tracing route to google.com [72.14.207.99]

over a maximum of 30 hops:

  1    1 ms    1 ms    <1 ms  DD-WRT [192.168.1.1]

  2    7 ms    6 ms    6 ms  74-132-48-1.dhcp.insightbb.com [74.132.48.1]

  3    8 ms    6 ms    6 ms  74-132-0-185.dhcp.insightbb.com [74.132.0.185]

  4    9 ms    7 ms    7 ms  74.128.8.201

  5    13 ms    *      15 ms  so-7-1.car2.Chicago1.Level3.net [4.71.182.25]

  6    15 ms    17 ms    15 ms  ae-32-56.ebr2.Chicago1.Level3.net [4.68.101.190]

  7    30 ms    32 ms    34 ms  ae-2.ebr2.Washington1.Level3.net [4.69.132.70]

  8    35 ms    34 ms    35 ms  ae-3.ebr2.NewYork1.Level3.net [4.69.132.94]

  9    37 ms    35 ms    34 ms  ae-21-56.car1.NewYork1.Level3.net [4.68.97.180]

10    36 ms    34 ms    40 ms  GOOGLE-INC.car1.NewYork1.Level3.net [4.71.172.86

]

11    35 ms    35 ms    35 ms  72.14.236.213

12    46 ms    48 ms    47 ms  72.14.233.115

13    45 ms    48 ms    48 ms  66.249.94.96

14    56 ms    53 ms    54 ms  72.14.236.134

15    45 ms    49 ms    47 ms  eh-in-f99.google.com [72.14.207.99]

Trace complete.

there isnt a problem with level3.. but their icmp packets are set to a low priority..

Link to comment
Share on other sites

×
×
  • Create New...