I already posted this in the thread regarded connection issues after the data server move, but I've been having the exact same issue.

This is the traceroute. As you can see, the issue begins at jump 11, which is in Chicago. Also note the massive increase in ping when hitting that node as well, as big an increase as when the route jumps from Chicago to California, when the jump before that, also in Chicago, doesn't. I'm suspecting that this particular server is getting overloaded during peak hours.