@AaronBertrand that read-only shows on stack status for two reasons: (1) that read-only (while providing some function) is not "we're operating normally" is clearly visible (note the read only message does link to stack status) and (2) being internally consistent. (An alerting mechanism for the SE team it is not, but the mechanism to propagate "unwell" can do more than one thing).

@AaronBertrand another action item that should be on the list: show running read-only on stackstatus.net (it looked like "you" thought things were fine).

I've checked my copy of the Oxford Manual of Style (as used by Oxford University Press): in technical contexts (which this certainly is): use a thin space.

For me often because the normal code markup will apply syntax highlighting (and, as in the case, remembering the right magic to switch it off would take longer than adding the tags).