Massive Massive Lag - Midgardsormr and instance server

[Raist]

Tracing route to 199.91.189.74 over a maximum of 30 hops

<initial hops removed for security>
4 24 ms 24 ms 23 ms xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
5 31 ms 30 ms 38 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
6 28 ms 30 ms 27 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 81 ms 78 ms 83 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 82 ms 81 ms 81 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.165]
9 90 ms 90 ms 91 ms te0-3-0-2.ccr21.dca01.atlas.cogentco.com [154.54.2.46]
10 97 ms 97 ms 97 ms te0-7-0-14.ccr21.jfk02.atlas.cogentco.com [154.54.41.6]
11 * * * Request timed out.
12 68 ms 69 ms 79 ms 38.122.42.34
13 71 ms 68 ms 69 ms 10.2.2.1
14 104 ms 70 ms 68 ms 192.34.76.2
15 70 ms 68 ms 70 ms 199.91.189.234
16 68 ms 69 ms 72 ms 199.91.189.74

Trace complete.

Deja Vu.

Looks like a similar issue as when it got flakey over the weekend. Different IP's, but the same groups appear to be in play. Coming across the border, over near Washington, cutting across British Columbia and BAM---full time out and retry. Good old Cogent Communications / PSINet seems to be dropping the ball again.

http://whois.arin.net/rest/net/NET-154-54-0-0-1/pft
http://whois.arin.net/rest/net/NET-38-0-0-0-1/pft

Edit:Looking at it more closely, after the 4th trace I ran, the BC finally starting responding on all three pings again, but then the JFK02 started acting up, dropping at least one ping the next 3 runs. The ones that get through at that BC hop though are breaking the 130ms line, then it drops immediately back to the 70's for the rest of the run.

Consistently seems to be something unstable about crossing the border or cutting across to Montreal.