Anyone currently experiencing a slow response time from stackoverflow.com? I received no response or 504 bad gateway error.

share|improve this question
2  
The intertubz are clogged. – Robert Harvey May 26 '10 at 18:47
I got 502 Bad Gateway once. The ping time is significantly longer than meta (by a factor of 2 to 10.) – KennyTM May 26 '10 at 18:47
@Robert: You weren't supposed to delete the first comment. :) – Jon Seigel May 26 '10 at 19:07
How do I accept an answer to this question? Until one of the employees verifies the event that caused the slow response time. – Michael Kniskern May 26 '10 at 20:25
I'm having trouble with SF right now. The question page loads pretty quickly (or appears to) but it IE8 still says "Waiting for serverfault.com/..."; in the status bar and some of the controls (mark as answer) won't work – user131750 Jun 3 '10 at 13:53

3 Answers

I saw this a moment ago as well, but I think the actual slow part is the sstatic.com domain they use for static content. I think this usually means they just updated a file or two there and it's slow for a few minutes while everyone has to update their browser cache with the new version of whatever they changed.

share|improve this answer

Seems to be back to normal now, but while it happened I was awarded a badge. Maybe the badge-awarding batch process is to blame.

share|improve this answer
6  
Maybe you're to blame! ಠ_ಠ – Bill the Lizard May 26 '10 at 18:49
4  
Hey, where's my badge? – Robert Harvey May 26 '10 at 18:49
1  
@Bill: When I give a Nice Answer, Stack Overflow immediately stops all activity until it has awarded me with my rightly deserved badge. Sounds appropriate to me. – sth May 27 '10 at 0:24
1  
Oh right, I forgot about the medal ceremony. Congratulations. ;) – Bill the Lizard May 27 '10 at 3:20

It was that way a few minutes ago during this catastrophe http://meta.stackoverflow.com/questions/51307/extra-votes-to-migrate-lead-to-multiple-posts but now that the question is deleted it seems to be going at normal speeds

share|improve this answer
Perhaps the update that Joel implies is what actually caused that catastrophe. If not the update, then the act of updating itself, perhaps. – Grace Note May 26 '10 at 18:58
I actually think it's more likely the "catastrophe" caused one of the devs to rush out a fix and cause the update. – Joel Coehoorn May 26 '10 at 19:13

You must log in to answer this question.

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