We've now fixed the issue. It was caused by an upgrade to our search infrastructure. An issue with our search server resulted in the API server not being able to start. We corrected the underlying issues and everything should be back to normal now.

Our backend server is offline. We're investigating the cause.