Take A Look at This TraceRoot Is Something Wrong?

Question

Tracing route to us.port.msn.com.nsatc.net [207.68.173.76]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1

2 9 ms 2 ms 9 ms c-75-69-136-1.hsd1.ma.comcast.net [75.69.136.1]

3 7 ms 3042 ms 8 ms ge-3-1-ur01.gloucester.ma.boston.comcast... [68.86.227.249]

4 9 ms 10 ms 9 ms be-15-crs01.woburn.ma.boston.comcast.net [68.87.145.153]

5 10 ms 10 ms 10 ms 68.85.162.69

6 15 ms 1554 ms 15 ms te-3-1-ar01.chartford.ct.hartford.comcas... [68.86.90.58]

7 26 ms 19 ms 18 ms pos-0-3-0-0-cr01.chicago.il.ibone.comcas... [68.86.90.57]

8 18 ms 17 ms 17 ms xe-11-0-0.edge1.NewYork2.Level3.net [4.71.186.1]

9 27 ms 18 ms 20 ms vlan69.csw1.NewYork1.Level3.net [4.68.16.62]

10 32 ms 19 ms 16 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.134.81]

11 39 ms 49 ms 53 ms ae-2.ebr1.Chicago1.Level3.net [4.69.132.65]

12 46 ms 39 ms 49 ms ae-68.ebr3.Chicago1.Level3.net [4.69.134.58]

13 64 ms 68 ms 71 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]

14 92 ms 90 ms 1628 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53]

15 89 ms 90 ms 89 ms ae-21-52.car1.Seattle1.Level3.net [4.68.105.34]

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

Answer 1

You are tracing a company with a firewall. It is going to bounce and return until it hits the firewall. That is what is causing the time out. Large companies do not want to be pingable, cause if millions of people start pinging them it will lag them to no end. Its there, just can't get to it by ping. That Denver to Seattle hop is the one I see that is trouble. There is nothing you can do about it though. If you have a overall ping of around 150-200 from over seas that is about all you can expect.

Try pinging a regular ip address..or something like www.yahoo.com

Answer 2

Here you are (from UK as you can see).

  1    <1 ms    <1 ms    <1 ms  192.168.6.1

  2     1 ms    <1 ms    <1 ms  dslmodem.domain.actdsltmp [192.168.0.1]

  3    48 ms    14 ms    14 ms  cr0.wrbrix.uk.easynet.net [XX.x*x.XX.XX]

  4    15 ms     9 ms    10 ms  fe2-0-2.ar11.bllon.uk.easynet.net [82.111.98.65]

  5    12 ms    11 ms    11 ms  ip-89-200-130-101.ov.easynet.net [89.200.130.101

]

  6    10 ms    11 ms    10 ms  ip-89-200-130-100.ov.easynet.net [89.200.130.100

]

  7    79 ms    78 ms    79 ms  so0-7-0-0.gr10.sdnyc.us.easynet.net [87.86.77.11

1]

  8    78 ms    79 ms    78 ms  68.86.89.145

  9    81 ms    82 ms    82 ms  68.85.162.74

10    86 ms    89 ms    84 ms  po-15-ar02.woburn.ma.boston.comcast.net [68.87.1

45.154]

11    87 ms    87 ms    86 ms  te-9-1-ar01.woburn.ma.boston.comcast.net [68.87.

146.190]

12    88 ms    87 ms    87 ms  te-9-1-ur01.gloucester.ma.boston.comcast... [68

.87.146.189]

13    88 ms    88 ms    87 ms  c-75-69-136-1.hsd1.ma.comcast.net [75.69.136.1]

Sorry, text formatting is a bit messy.

Answer 3

As far as I can tell, the page you are trying to reach does not exist, which is why your request times out.

The rest is normal