Hey all, I got word from one of our lead webdevs 3 hours (and change) ago that the problem has been identified and fixed. Yes, I confirm it was in the middle of a Friday night CET - how's that for dedication? :)
I was driving at the time, so posting about it would've been rather unwise, as I'm sure (most of) you will agree. :D

Sorry about the issue, and thanks a bunch for reporting it, both here and via Support. :)