Comment 9 for bug 844631

I've uncriticaled this because its a *symptom* not a cause of users seeing OOPs: fastdowntime is the cause, and we'll still be generating OOPSes when this event happens: the appservers cannot tell fastdowntime from the-network-is-broken.

I'd also like to note that we should include the OOPS in the 503 page (but very small, in a corner, or even just in the source) - so that if someone gets one of these when we are *not* deploying, we can track it down. e.g. users don't need to see it, but if some hits the page and asks in IRC, we can tell them what to do to get the OOPS id out.