Customers on cluster 1 may notice some slowness and 503 errors on their sites due to a currently unknown issue. Our team is already working on it and we should hopefully have the issue resolved shortly.
As soon as we have more information on the matter, we’ll post it here.
Update: We’ve been watching things for a little while and we feel like it’s safe to say that everything is clear now. The issue appears to have been an I/O problem with one of the servers on the cluster, but our team and the folks at FireHost managed to get things all sorted out.