New "Service Busy" responses beginning during high load

In response to community feedback, we're planning to change the status code returned to 503 Service Unavailable, so as to avoid unintentionally conflating rate limits with API load. The Retry-After header and problem document will remain the same.

12 Likes