Looks fixed now!

Getting 500 errors on all* the profile pages, on all the main (non-meta) SE websites:

I know you're fixing it, but I'm just curious what happened?

*: well, I cannot reproduce it on stackexchange.com, maybe there are other exceptions, but something got fishy anyways.


It was a bad roll out of DB migrations + code at the same time. DB migrations happen when meta is built. So it was a case of old (pre-migration) code running against new DB schema. The issue fixed itself once everything was deployed to all servers across all tiers (meta & sites).

Rest assured, The Wheel of Blame has been spun.

  • 3
    Thank you for not putting a meme in your post. – Deer Hunter Feb 12 '16 at 15:07

You must log in to answer this question.

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