I just saw this:

This site is currently in read-only mode; we’ll return with full functionality soon.

What happened? Was there some sort of hacking incident?

closed as off-topic by Martijn Pieters, Aza, hims056, Azik, Matt May 7 '14 at 13:38

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." – Martijn Pieters, Aza, hims056, Azik, Matt
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 7
    Probably maintenance or new patch deployed – Hugo Dozois Nov 24 '13 at 18:20
  • 31
    Clever attackers destroyed the entire site and replaced it with an exact duplicate. Those bastards. – Shog9 Nov 24 '13 at 18:26
  • 18
    Who cares? Seriously. Does there need to be a Meta question for every 10-second outage now? If it's something major, it's going to be on stackstatus.net – Pëkka Nov 24 '13 at 18:29
  • 14
    The site goes to a read-only mode whenever Jon Skeet logs out, so he won't be under threat from any other users. But that usually only lasts a couple of minutes. Most likely this was his weekly nap time. – Bart Nov 24 '13 at 18:37
  • That's a hellban put on users after we take a vote on whether or not we like them. Sorry, voted for you, but these other guys, pfft. – Won't Nov 24 '13 at 20:50
  • With such a good answer, I don't see how this question was considered so useless: 17 downvotes so far! Except people here are too harsh on questions sometimes. – cregox May 6 '14 at 21:32
  • @Cawas Meh, whatever. The downvotes don't really bother me- I have a pretty thick skin :P Thanks for looking out for me, though! – Blue Ice May 7 '14 at 1:17
  • 3

EDIT: This answer only applies to the read only/downtime event in November 2013. For up to date Stack Exchange status, check @StackStatus on Twitter and/or stackstatus.net

From @stackstatus on Twitter:

We are failing over to our secondary SQL setup, there may be a slight interruption. #stackoverflow #stackexchange

Its probably related to that

And scrolling a little further down the Twitter timeline I ran into this from Nick Craver:

Typically we have thousands of plans in cache, but after a routing job, it’s as if caching has been disabled #sqlhelp


The best place to check for a current answer to this question seems to be to check @stackstatus on Twitter.

  • 3
    See the accepted answer from 5.5 months ago... – Nick Stauner May 6 '14 at 21:08
  • @Nick Stauner Should I then delete the specific instance information from the old accepted answer? I used the above answer gratefully to find out why it was happening again. : ) – Fred May 6 '14 at 21:37
  • I suppose you could suggest an edit to it that makes it clearer that you can check the page for updates at any time, but no guarantees it'd be accepted of course. Since your answer doesn't add anything unique beyond that, I fear you might be courting downvotes ;) (Not that I'm encouraging anyone to do so with this comment...seems a little pointless.) – Nick Stauner May 6 '14 at 21:42
  • @Nick is correct, twitter is already mentioned and linked to from the other answer, maybe comment there or edit might fit but not new answer just to tell "twitter is the place to check". – Shadow May 6 '14 at 22:03
  • 2
    I've updated my answer to point out that the answer only applies to the event that happened in November 2013. – Steven V May 7 '14 at 1:16

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