I am getting Connection refused on a lot of links
I am also seeing errors. Here is a result from a random link on the frontpage:
~$ curl http://news.yahoo.com/half-girls-south-sudan-forced-marry-140334618.html
<HEAD><TITLE>Connection refused</TITLE></HEAD>
<BODY BGCOLOR="white" FGCOLOR="black">
<FONT FACE="Helvetica,Arial"><B>
Connection refused</B></FONT>
<!-- default "Connection refused" response (502) -->
</BODY>
My path to yahoo:
~$ traceroute news.yahoo.com
traceroute to news.yahoo.com (66.94.233.187), 30 hops max, 60 byte packets
1 10.0.2.1 (10.0.2.1) 1.088 ms 1.265 ms 3.917 ms
2 olp-67-217-152-5.olp.net (67.217.152.5) 3.436 ms 3.629 ms 4.125 ms
3 router.olp.net (67.217.151.97) 2.515 ms 2.753 ms 2.991 ms
4 olp-67-217-152-34.olp.net (67.217.152.34) 4.317 ms 4.555 ms 4.788 ms
5 gi1-6.ccr01.tul01.atlas.cogentco.com (38.104.198.73) 39.056 ms 39.280
ms 39.502 ms
6 te0-2-0-7.ccr22.dfw01.atlas.cogentco.com (154.54.5.13) 11.012 ms
7.656 ms 7.913 ms
7 te0-6-0-5.ccr22.dfw03.atlas.cogentco.com (154.54.82.26) 8.359 ms
te0-1-0-5.ccr22.dfw03.atlas.cogentco.com (66.28.4.134) 8.541 ms
te0-6-0-1.ccr22.dfw03.atlas.cogentco.com (154.54.6.62) 9.064 ms
8 te4-1.mag01.dfw03.atlas.cogentco.com (154.54.81.38) 8.792 ms 9.283 ms
9.588 ms
9 yahoo.dfw03.atlas.cogentco.com (154.54.10.138) 9.813 ms 10.033 ms
yahoo.dfw03.atlas.cogentco.com (154.54.10.6) 10.273 ms
10 ae-2-d100.msr1.mud.yahoo.com (216.115.104.105) 10.771 ms
ae-2-d111.msr2.mud.yahoo.com (216.115.104.111) 11.129 ms
ae-1-d111.msr2.mud.yahoo.com (216.115.104.103) 11.349 ms
11 te-6-2.fab2-a-gdc.mud.yahoo.com (209.191.78.153) 12.060 ms
te-6-2.fab1-a-gdc.mud.yahoo.com (209.191.78.145) 11.848 ms
te-8-1.fab1-a-gdc.mud.yahoo.com (209.191.78.133) 12.270 ms
12 te-8-1.bas1-1-prd.mud.yahoo.com (66.94.233.225) 8.665 ms 9.011 ms
unknown-66-94-233-x.yahoo.com (66.94.233.237) 8.528 ms
13 * * *
14 * * *
In a message written on Fri, Mar 08, 2013 at 08:48:00AM -0800, Philip Lavine wrote:
I am getting Connection refused on a lot of links
I think many of their servers were telecommuting from remote data
centers, and were told they were no longer needed if they couldn't
come into the office...
The Yahoo sites must be working fine when accessed from Yahoo's
office, but since working from home is banned, the workers are not
able to check! 
Rayson
I had an unusually large number of page load timeouts against some of
Yahoo's IPv6 test points between 10:34 am and 11:27 am (Central) on Friday.
I suspect that our experiences were related.
Frank