We’re rolling out a fix right now - hopefully should be back up in 10!
Will keep this open until we’ve added monitoring + ops fixes to prevent this from happening again. We usually get paged for serious bugs like this but it looks like there’s something wrong with our alerting setup.