What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 131 Stack Exchange communities.

I've been having issues accessing stackoverflow for the last couple of days.

Today, I've tracked it down to having issues getting content from the CDN. It takes an age to load the page and it is missing the CSS and js files that make it look presentable, ad aloow voting etc.

If I view source and try to download the linked css file directly I get the follwoing message:

"The proxy cannot establish a connection to the web server: cdn.sstatic.net / 69.174.57.102:80".

This is accessing from work in the UK. I've not tried from home, yet.

Is this issues affecting anyone else? Is it just my office proxy and I need to catch our IT dept? (I'm not aware of any other websites not working - just the stackexchange family using cdn.sstatic.net).

Also, I can connect to http://sstatic.net, it just the cdn. subdomain

EDIT: Also, any reason why meta.stackoverflow.com does not use the cdn?

EDIT: The issues appears to have resolved itself .. not sure who did what where...

share|improve this question
1  
I'm also seeing the problem, in my office in the UK. Your office doesn't happen to use WebRoot Proxy as a filtering provider, does it? –  Matt Gibson Jul 20 '11 at 10:19
    
On further investigation, my problem seems to be a DNS lookup: I get "DNS lookup for the web server name (cdn.sstatic.net) failed." if I try to visit the URL for one of the stylesheet directly. –  Matt Gibson Jul 20 '11 at 10:22
    
@Matt: Yes, I believe we do have a WebRoot Proxy. - but the issue appears to have now resolved itself. –  Grhm Jul 20 '11 at 10:43
    
I've found WebRoot proxy unreliable on DNS lookups on at least another couple of occasions this week (I think with their system it's their proxy server that does the DNS lookup, so I guess it's just a bit rubbish at the moment.) They also seem to be blocking all sorts of random things -- my image placeholders have started failing because they've blocked placehold.it for "Media Sharing"! –  Matt Gibson Jul 20 '11 at 10:48
    
    
@Bobby Those all appear to relate to failure of the CDN/connection to the CDN after a successful DNS lookup, rather than what I'm seeing. But I suppose that they're technically duplicate questions, even if the answer isn't the same... (Incidentally, I just temporarily hardcoded a CDN IP address in my hosts file, and it's working fine now, so it's definitely a DNS issue for me.) –  Matt Gibson Jul 20 '11 at 10:57
    
This is still affecting me. Cannot connect to cdn.sstatic.net at all, so stackoverflow gets served with missing content. Some stuff is usable (can post a question) but some other functions don't work (cannot post comments). meta.stackoverflow.com works fine. Maybe as a workaround, make changes necessary to have stackoverflow functional even without cdn served content? –  user1394355 May 16 '12 at 13:51
    
C:\Windows\System32\drivers\etc>tracert cdn.sstatic.net Tracing route to sstatic.stackexchange.netdna-cdn.com [67.201.31.70] over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. ... until it gives up. –  user1394355 May 16 '12 at 13:53
    
having similar issue. –  Sisir Jun 13 '13 at 9:02
    
SO has been down for me for 10 days now. Considering the Google result for "jquery ajax error NaN" this can be called a catastrophe. I'm in Africa. I'm told SO was fine (on the speedy side) here for years. What happened on the 1st of august? –  xaccrocheur Aug 6 at 10:26
1  
@xaccrocheur You might want to raise this as a separate question - it not going to be noticed as a comment here.. –  Grhm Aug 6 at 10:51

1 Answer 1

up vote 5 down vote accepted

Well, given that we both have the same problem and we both seem to be using WebRoot Proxy, I'd say that the issue is that WebRoot Proxy is having problems resolving the IP address for cdn.sstatic.net. The DNS lookup error I see when I try to visit one of SO's stylesheets in my browser certainly seems to come from WebRoot Proxy's servers rather than anything local.

I've tested this by temporarily making a local override for one of the CDN's local IP addresses (69.174.57.102) in my hosts file, and that has allowed me to successfully see Stack Overflow's stylesheets again.

The long-term solution is to get your IT people to get on to the providers of the WebRoot Proxy service and ask them nicely to investigate their DNS lookup failures, I'd say.

share|improve this answer
1  
I don't think my issue was WebRoot failing to do DNS lookups. The error message (as shown in my question) quoted the server name and IP address. –  Grhm Jul 20 '11 at 11:08
    
@Grhm Good point! I hadn't noticed the IP address in your post. Interestingly, my problem seems to have disappeared now, though I've removed the IP address hardcoding and flushed my cache. I still suspect some transient problems at the proxy side of things are the cause for both of us... –  Matt Gibson Jul 20 '11 at 16:18
    
@Matt Gibson i tried to ping 69.174.57.102 it is not reachable 108.161.190.2 Ip is returning. which is content provider for stackoverflow –  bikram990 Jul 12 '13 at 10:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .