If only more people understood this... no matter how many times it's been shown to be true, some just refuse to accept it. Guess it's just easier to whine and complain then to follow the proper support process and actually get it fixed. All it took to get mine resolved was to take a few tracerts, open a suppoprt ticket with SE, and send a few emails to my ISP. Sure, it's been an ongoing process, but Time Warner has been working on it, and it continually improves.
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\DarrenBoyd>tracert 199.91.189.74
Tracing route to 199.91.189.74 over a maximum of 30 hops
<initial hops removed for security>
4 26 ms 23 ms 27 ms xe-7-0-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.42]
5 26 ms 31 ms 32 ms bu-ether34.atlngamq46w-bcr00.tbone.rr.com [107.14.19.48]
6 28 ms 28 ms 29 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 80 ms 79 ms 80 ms te0-0-0-10.ccr21.atl02.atlas.cogentco.com [154.54.12.109]
8 79 ms 75 ms 74 ms be2050.ccr21.atl01.atlas.cogentco.com [154.54.0.165]
9 88 ms 86 ms 91 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
10 96 ms 96 ms 94 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 121 ms 111 ms 107 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
12 49 ms 51 ms 50 ms 38.122.42.34
13 63 ms 64 ms 64 ms 10.2.2.1
14 64 ms 99 ms 64 ms 192.34.76.2
15 63 ms 63 ms 68 ms 199.91.189.234
16 63 ms 63 ms 63 ms 199.91.189.74
Trace complete.
They've brought me back to Charlotte again, but this time around I'm not getting the 25-48% packet loss. It's still pulling in around 7% during prime time, but it's a VAST improvement. Not bad for about 15 minutes of work pulling in the PROPER people to resolve the problem.