We saw an increased number of 503 error rates between 1:40-1:50 UTC. We've deployed a fix and are monitoring now.