Re: yahoo, again?

[Mike Tancsa <mike () sentex net>]

At 10:04 PM 2/21/2000 -0500, David Diaz wrote:
>Yep seeing the same.  It was working around 8:30PM EST


Some paths seem to be working just fine

  1 nero-eugene-hub.oregon-ix.net (198.32.162.2) [AS 2914] 4 msec 0 msec 0 
msec
  2 eugene-isp.nero.net (207.98.64.41) [AS 3701] 0 msec 4 msec 0 msec
  3 xcore2-serial0-1-0.SanFrancisco.cw.net (204.70.32.5) [AS 3561] 12 msec 
12 msec 12 msec
  4 bordercore1.SanFrancisco.cw.net (166.48.12.1) [AS 3561] 12 msec 12 
msec 12 msec
  5 frontier-communications.SanFrancisco.cw.net (166.48.13.242) [AS 3561] 
272 msec 112 msec 136 msec
  6 pos4-2-155M.cr1.SNV.gblx.net (206.132.150.25) [AS 3549] 80 msec 80 
msec 84 msec
  7 pos0-0-2488M.hr8.SNV.gblx.net (206.132.254.37) [AS 3549] 80 msec 84 
msec 80 msec
  8 208.178.22.58 [AS 3549] 80 msec 84 msec 80 msec
  9 www.yahoo.com (204.71.200.74) [AS 3549] 80 msec 80 msec 80 msec

But others not.

marble# traceroute www.yahoo.com
traceroute to www.yahoo.com (204.71.200.67), 30 hops max, 40 byte packets
 1  iolite-gate (199.212.134.14)  0.410 ms  0.366 ms  0.319 ms
 2  hespler-border (205.211.165.178)  0.443 ms  0.447 ms  0.470 ms
 3  206.222.95.25 (206.222.95.25)  1.116 ms  0.993 ms  0.960 ms
 4  206.222.95.21 (206.222.95.21)  6.231 ms  4.504 ms  5.505 ms
 5  brdr1-tor.tor.rns.net (206.222.64.2)  4.992 ms  6.241 ms  4.302 ms
 6  sl-gw21-chi-5-1-0.sprintlink.net (144.232.188.149)  28.330 ms  28.046 
ms  28.032 ms
 7  sl-bb11-chi-1-1.sprintlink.net (144.232.10.37)  28.432 ms  28.785 
ms  27.931 ms
 8  sl-bb10-chi-9-0.sprintlink.net (144.232.10.49)  39.518 ms  59.201 
ms  67.531 ms
 9  sl-bb11-nyc-5-1.sprintlink.net (144.232.9.149)  68.574 ms  43.531 
ms  53.200 ms
10  sl-bb1-nyc-4-0-0.sprintlink.net (144.232.7.10)  166.779 ms  189.807 
ms  184.812 ms
11  sl-intsys-8-0-0-155M.sprintlink.net (144.232.171.130)  45.339 
ms  48.740 ms  68.757 ms
12  * * *
13  * * *
14  * * *


        ---Mike