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 can't reach Stack Overflow any more. Yesterday, the status blog said:

After our weekly index optimization, SQL Server is no longer caching our query plans causing high CPU load. This will likely overload our CPUs tomorrow if we don’t get this resolved.

Is this happening now?

share|improve this question

closed as off-topic by Emrakul, Bart, hims056, Mołot, Duncan Nov 25 '13 at 10:52

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "The problem described here can no longer be reproduced. Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question." – Emrakul, Bart, hims056, Mołot, Duncan
If this question can be reworded to fit the rules in the help center, please edit the question.

3  
Seems like it. MSO is the only site I'm able to load. –  Jamal Nov 25 '13 at 9:10
    
Last update from @StackStatus was: "StackExchange Status ‏@StackStatus 6h #stackoverflow is now back online, we are continuing to work on the issue." - Nothing saying that the issue itself has been fixed. So no, looks like it's still an issue. –  JonW Nov 25 '13 at 9:10
3  
Don't know why this is getting downvotes. I'd say it's pretty well borked. And it's not recovering for me. –  Emrakul Nov 25 '13 at 9:16
    
@JonW the blog post says We are currently working with Microsoft to resolve this issue. You may notice short outages while we troubleshoot. We will do our best to minimize the impact –  Shadow Wizard Nov 25 '13 at 9:17
    
I have no issues with The Workplace, but stack overflow itself is not working. –  jmac Nov 25 '13 at 9:18
    
@Emracool even Google or Facebook suffer outage from time to time, no site has 100% uptime. If this will go on for long time (hour or so) then we can start yelling here on Meta. :) –  Shadow Wizard Nov 25 '13 at 9:18
2  
Stack Overflow should just report a stack overflow for teh lulz. –  Jamal Nov 25 '13 at 9:19
    
@Sha An ASPX error like that usually doesn't recover on its own, as far as I've seen. That's indicative of a more serious error. I agree, though, maybe would have waited an hour or three before posting :] –  Emrakul Nov 25 '13 at 9:19
6  
Place your bets on how many more Meta StackOverflow posts get raised reporting this outage... –  JonW Nov 25 '13 at 9:21
    
And there we go. Now the site is actually borked. –  Emrakul Nov 25 '13 at 9:21
1  
I have no problem deleting this. Shall I? –  juergen d Nov 25 '13 at 9:21
    
@Emracool this kind of error just means there was error even in the error page, nothing too fancy or serious. If you would see Stack Trace then we got to start worrying. :) –  Shadow Wizard Nov 25 '13 at 9:21
    
@Emracool huh... the most offline I can get is the "we are offline" message –  Jan Dvorak Nov 25 '13 at 9:21
3  
@Emracool not offline, read only mode. There's a difference. –  Shadow Wizard Nov 25 '13 at 9:22
2  
@juergend no, please don't delete we're having fun while the sites are doing roomba. –  Shadow Wizard Nov 25 '13 at 9:23

1 Answer 1

up vote 16 down vote accepted

We're playing SQL hot potato. Today may be a tad... "fun" while we find the gremlins.

Looks like we're stable as I write this though.

share|improve this answer
1  
Good luck guys. Hope you slove the problems soon! –  rekire Nov 25 '13 at 9:26
    
@Kevin will it affect the ETA to deliver the new top bar across all sites? –  Shadow Wizard Nov 25 '13 at 9:30
    
If these problems will last a while, is it possible to put up a banner on the main page saying so? (Have fun! /grin) –  Emrakul Nov 25 '13 at 9:47
    
@ShaWizDowArd - It is effecting all development. We will wait util we have a fix or we know enough to work around the issue. –  Oded Nov 25 '13 at 10:00
    
@Oded it's still rev 2013.11.22.1677 - so will you put new build with those breaking changes rolled back? (to deploy all the bug fixes done in those last few days :)) –  Shadow Wizard Nov 25 '13 at 10:01
3  
@ShaWizDowArd - The problem is with SQL Server. We can't roll back to a prior version of SQL Server. –  Oded Nov 25 '13 at 10:03
    
@Oded true enough... good luck with that! :) –  Shadow Wizard Nov 25 '13 at 10:04

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