My problem is similar, I am on Midgardsormr. And when I run a trace route to the server address I get these results:
Tracing route to 199.91.189.28 over a maximum of 30 hops
1 8 ms 7 ms 7 ms d4-50-1-34.try.wideopenwest.com [50.4.34.1]
2 8 ms 9 ms 8 ms 76-73-166-97.knology.net [76.73.166.97]
3 9 ms 10 ms 8 ms 76-73-167-214.knology.net [76.73.167.214]
4 9 ms 8 ms 10 ms 76-73-167-89.knology.net [76.73.167.89]
5 365 ms 36 ms 9 ms 76-73-167-66.knology.net [76.73.167.66]
6 10 ms 10 ms 11 ms xe-5-1-0.bar1.Cincinnati1.Level3.net [4.59.40.17
]
7 38 ms 37 ms 38 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 * 38 ms 38 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
9 39 ms 39 ms 38 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
10 * * * Request timed out.
11 42 ms 42 ms 42 ms 192.34.76.2
12 43 ms 42 ms 42 ms 199.91.189.234
13 42 ms 43 ms 45 ms 199.91.189.28
Trace complete.
EDIT: This one was taken about 10 minutes later, at 7:10pm EST
Tracing route to 199.91.189.28 over a maximum of 30 hops
1 8 ms 8 ms 7 ms d4-50-1-34.try.wideopenwest.com [50.4.34.1]
2 8 ms 9 ms 8 ms 76-73-166-97.knology.net [76.73.166.97]
3 8 ms 8 ms 8 ms 76-73-167-214.knology.net [76.73.167.214]
4 8 ms 9 ms 9 ms 76-73-167-89.knology.net [76.73.167.89]
5 8 ms 9 ms 8 ms 76-73-167-66.knology.net [76.73.167.66]
6 11 ms 11 ms 11 ms xe-5-1-0.bar1.Cincinnati1.Level3.net [4.59.40.17]
7 * 38 ms 38 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
8 * * * Request timed out.
9 39 ms 38 ms 39 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
10 * * * Request timed out.
11 40 ms 41 ms 39 ms 192.34.76.2
12 41 ms 40 ms 41 ms 199.91.189.234
13 41 ms 42 ms 41 ms 199.91.189.28
Trace complete.
Seems to be right out of Level 3 is where the problems start. Not sure what's going on with hop 10.
The problems get worse as the night goes on. Between 7:00pm to 11:00pm EST are pretty bad.
I hope this helps a little bit. I'm sure other people are going to be having similar problems.
My ISP is Wide Open West