Its not globix it is global crossing. Globix wishes they had Yahoo as a customer. Not bloody likely. Anyway, It seems that some mirrors are up, I reached img3.yahoo.com (204.71.200.243) I would suggest that you read the traceroute *header* more carefully. Retrying the target of my original trace shows that it is back but look at the delay, something seriously wrong between San Francisco and Sierra Nevada (guessing SNV translation). Especially if those circuits are to be believed -- OC-48 ....(one day some sub-T1 provider is going to name their circuits OC-x ... :-) ) 8 pos8-0-622M.wr2.sfo1.globalcenter.net (206.132.110.89) 89.660 ms 91.547 ms 84.731 ms 9 * pos4-0-622M.cr2.SNV2.gblx.net (206.132.254.58) 219.363 ms * 10 pos7-0-622M.cr2.SNV.gblx.net (206.132.151.22) 219.821 ms 218.671 ms 234.0 88 ms 11 pos1-0-2488M.hr8.SNV.gblx.net (206.132.254.41) 224.825 ms 221.514 ms 219. 169 ms 12 208.178.22.58 (208.178.22.58) 217.125 ms * 217.250 ms 13 img5.yahoo.com (204.71.200.245) 225.197 ms 224.276 ms 224.044 ms ----- Original Message ----- From: "Christian Nielsen" <cnielsen@nielsen.net> To: "Dana Hudes" <dhudes@panix.com> Cc: <nanog@merit.edu> Sent: Monday, February 21, 2000 10:38 PM Subject: Re: yahoo, again?
maybe it is your provider, maybe it is Globix, maybe it is GBLX... but it works from where I sit.
7 pos4-3-155M.cr2.SNV.gblx.net (206.132.150.242) 1.791 ms 1.773 ms 1.742 ms 8 pos1-0-2488M.hr8.SNV.gblx.net (206.132.254.41) 2.317 ms 1.847 ms 2.285 ms 9 208.178.22.58 (208.178.22.58) 2.880 ms 2.497 ms 2.517 ms 10 www2.yahoo.com (204.71.200.67) 2.582 ms 2.260 ms 2.848 ms
I would keep trying the upstreams till you found the problem.
On Mon, 21 Feb 2000, Dana Hudes wrote:
Same here, different path traceroute to yahoo.com (204.71.200.245) -- snip -- 9 pos8-0-2488M.wr2.SFO1.gblx.net (206.132.110.110) 82.986 ms 82.334 ms 83.345 ms 10 pos1-0-2488M.cr1.SNV2.gblx.net (208.48.118.118) 83.137 ms 84.088 ms 97.758 ms 11 * * * ^C
Altavista and Excite are up
----- Original Message ----- From: David Diaz To: dbird@bpnetworks.com ; nanog@merit.edu Sent: Monday, February 21, 2000 10:04 PM Subject: Re: yahoo, again?
Yep seeing the same. It was working around 8:30PM EST
4 ga0380.rt2.mia.netrail.net. (205.215.24.2 ): 28ms 28ms 29ms 5 ga031.rt2.atl.netrail.net. (205.215.61.26 ): 53ms 81ms 49ms 6 fgc.atl.netrail.net. (205.215.1.66 ): 51ms 53ms 50ms 7 pos2-1-155m.cr2.atl1.gblx.net. (206.132.115.125): 50ms 50ms 58ms 8 * * ?Cancelled by user?
At 6:56 PM -0800 2/21/00, David Bird wrote:
5 san1.dfw2.verio.net (129.250.2.242) 40.465 ms 39.994 ms 40.208 ms 6 dfw2.dfw3.verio.net (129.250.3.74) 40.082 ms 40.07 ms 39.986 ms 7 s11-1-0.ar1.DAL1.gblx.net (206.132.119.125) 40.922 ms 40.487 ms 40.493 ms 8 pos2-0-155M.cr2.DAL1.gblx.net (206.132.119.117) 41.231 ms 40.6 ms 40.704 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * *
--
David Bird dbird@bpnetworks.com http://www.bpnetworks.com/
Thank you, David Diaz Chief Technical Officer Netrail, Inc
email: davediaz@netrail.net, davediaz@fla.net, cougar@mail.rockstar.org pager: davediaz@bellsouthips.com NOC: 404-522-1234 Fax: 404 522-2191
----------------------------------- Build 1: 46 cities nationwide -- COMPLETE Build 2: 80 OC48s Nationwide [no typo]
++ FAILURE IS NOT AN OPTION! ++ ------------------------------------