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

Is anyone else seeing SO and meta responding very slowly when clicking links, etc? I thought perhaps it was issues with my ISP at home, but I'm seeing the same sort of problems at work. Periodically it will take a few seconds when I click on a link to get a response. It seems to have started after yesterday's SO outage.

EDIT: Right now I can't seem to connect to SO at all. Downforeveryorjustme.com reports SO is out for everyone.

EDIT2: Seems back up now... I won't keep updating if it goes down again, though. Hope @Jeff posts something on his blog about why this is happening.

share|improve this question
    
Yeah it seems to go up and down for me at the moment. –  Kevin Mar 12 '10 at 14:49
4  
Meta has been fine for me, SO has been hit & miss. –  Jon Seigel Mar 12 '10 at 14:50
    
SO was completely wedged when I tried to load it a few minutes back... Now it's reasonably responsive. –  Shog9 Mar 12 '10 at 14:58
    
Confirmed, although I have the feeling it's acutally sstatic.net that's acting up. –  balpha Mar 12 '10 at 15:02
    
@balpha: That hasn't matched with my experience of it today (fwiw). That's been the problem any number of other times, but not (for me) today. –  T.J. Crowder Mar 12 '10 at 15:04
3  
This is getting really irritating. –  T.J. Crowder Mar 12 '10 at 15:15
    
Confirm, SO is slow here as well. –  Nick Craver Mar 12 '10 at 15:19
    
Maybe that would explain why there is less activity on meta –  jmfsg Mar 12 '10 at 15:31
    
Just took too long for your molecules to shift back into phase. –  squillman Mar 12 '10 at 15:32
    
@Downvoter - yeah, it's Friday (here and in Iceland) and not much activity. I'm still seeing slowdown on meta, but it's intermittent. –  tvanfosson Mar 12 '10 at 15:59
2  
Things appear back to normal from here. –  tvanfosson Mar 12 '10 at 19:16
    
Same here, SO was extremely slow all day but is fine now. This is the first time it wasn't ads.stackoverflow.com nor any other contributing domain (I think) but the site itself. (Germany) –  Pëkka Mar 12 '10 at 21:03
add comment

closed as too localized by ben is uǝq backwards, hims056, Lance Roberts, Bo Persson, animuson Apr 18 '13 at 16:25

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

2 Answers

up vote 8 down vote accepted

Last night we made a change to our network to the goal of simplifying our configuration. We have removed TProxy from our HAProxy servers and are now using X-Forwarded-For headers to track IPs. We also removed the IIS7 dynamic IP restrictions module from the IIS instances and are now using iptables / netfilter to control rate limiting. The default maximum number of connections that are tracked for iptables / netfilter is 32764 which we hit at around 5:00am PST. I bumped up this value to 65528 which solved the latency issues. We will continue to keep an eye on it.

share|improve this answer
3  
Hah! Tech-talk to confuse the audience! –  Pëkka Mar 12 '10 at 21:02
    
Isn't 65k very low? Why not set it to 200k so you won't run again into this problem relatively soon? –  Andreas Bonini Mar 12 '10 at 21:11
    
@Kop. I don't think the servers would handle 200k simultaneous connections being processed at the same time.. or at least not with any speed.. –  Earlz Mar 12 '10 at 21:22
add comment

oh noes!

I might have to actually do work today...

share|improve this answer
add comment

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