For about 2 weeks, multiple people (around 10 that I know of) in our company are having trouble accessing Stack Overflow; independently of the browser, and on Linux as well as Windows. The symptom is that assets loaded from cdn.sstatic.net keep waiting forever or until they time out.

On my machine the status is that at some point those requests time out and a version of the page without any images or CSS appears.

For some Windows users reboots help, for others it doesn't.

Meta Stack Overflow (now Meta Stack Exchange) always loaded for me.

A workaround for my machine was to disable IPv6 temporarily on Linux with the command echo 1 | sudo tee /proc/sys/net/ipv6/conf/all/disable_ipv6.

Note that no other site (that I visit) has been affected like this.

Update 2013-08-12: our network guy did some checking and insists the problem lies with Cloudflare. We seem to have issues when trying to connect to them with IPv6. We can't go around and disable our IPv6 Support since we need it for our internal infrastructure. We employ the following workaround (sadly only works with Firefox):

2. find the configuration key called network.dns.ipv4OnlyDomains
3. Set it to the following list of domains (or add them if you already have something in this key): cdn.sstatic.net,www.cloudflare.net,cdn-careers.sstatic.net
-
Sounds more like a problem in your network, to be honest. –  Time Traveling Bobby Jun 20 '13 at 7:19
Well, that's what it sounds like. But given that this only occurs with Stackoverflow and that IPv6 seems to be a factor and the many reports on meta regarding similar issues, it seemed fair that I would attempt to sollicit feedback from the admins. –  Boris Terzic Jun 27 '13 at 7:25
Does host -t AAAA cdn.sstatic.net resolve okay? If not, does using Google's DNS help, host -t AAAA cdn.sstatic.net 8.8.8.8? (Note that Meta does not use the CDN. Nice workaround!) –  Arjan Aug 12 '13 at 15:36
(Or, for Windows: nslookup -t=AAAA cdn.sstatic.net and nslookup -t=AAAA cdn.sstatic.net 8.8.8.8) –  Arjan Aug 12 '13 at 16:04
host -t AAAA cdn.sstatic.net seems to work fine, output: cdn.sstatic.net is an alias for sstatic.net.cdn.cloudflare.net. sstatic.net.cdn.cloudflare.net has IPv6 address 2400:cb00:2048:1::be5d:f43a sstatic.net.cdn.cloudflare.net has IPv6 address 2400:cb00:2048:1::be5d:f53a sstatic.net.cdn.cloudflare.net has IPv6 address 2400:cb00:2048:1::be5d:f63a sstatic.net.cdn.cloudflare.net has IPv6 address 2400:cb00:2048:1::be5d:f73a sstatic.net.cdn.cloudflare.net has IPv6 address 2400:cb00:2048:1::8d65:723b –  Boris Terzic Aug 14 '13 at 6:47

Can you provide us with details on your IPv6 address and network setup to team@stackoverflow.com - ask for it to be forwarded to Nick Craver and I'll take a look.

We've seen a few reports of IPv6 DNS request issues related to the new CDN, we're working with them on a resolution.

-
Congrats for the new avatar, I see the kid is growing up! :) –  Shadow Wizard Jun 20 '13 at 12:58
Sent the Details to team@stackoverflow.com and the problem persist across the company. If you need anything in addition to debug, please let me know. –  Boris Terzic Jun 27 '13 at 7:23
@Nick, just in case you missed it, and just in case it helps future investigations: see erpel's answer about MTU settings. –  Arjan Aug 26 '13 at 7:27
Any updates on this? I'm getting the same behavior (requests just stay open until they time out) still. Disabling IPv6 completely "solves" it... –  James B Oct 6 '13 at 8:42
I've been getting this for the last few weeks on my Windows 8 laptop. I disabled IPv6 in Firefox per the instructions above and it worked. –  Marc D Anderson Feb 9 at 22:31

For me, DNS always looked fine, but I also never got any http responses back from the CDN hosts.

Lowering the MTU on my tunnel interface from 1500 to 1300 restored stackoverflow availability instantly.

This could serve as a workaround but is also something that one might want to look at on the hosting site.