We've updated the server code on 18.104.22.168 to make it more responsive. We're keeping an eye on it to see for sure. One of the major differences is how long the server waits for a connection (it was waiting way, way too long before and that filled up all of its threads). We've cut that down as well as significantly increased the number of threads. In combination with no new assigns for this server for a while, this should drain it and get the server I/O back to normal.