Go to speedtest.net and click to change the server. Search Seattle, then look for and select Century Link. This is a close approximation to Bungie in Bellevue, WA... just a ccx Ross the lake from them, and Level3/Century link carries about 40% of the traffic coming off their network. As the test runs, watch the speeds closely. It will graph it as it goes along as well. It may ramp up real fast at the start because of buffering/bursting, but for the most part it should remain fairly constant or on a gentle slope. If the transfer is erratic, there may be a jitter problem with the latency... too much variance in the response times. In a game like D2 that is very sensitive to latency issues and doesn't do error correction via TCP (uses UDP), it can lead to dropped packets because packets may arrive too late (it may igore them if too far out of order). If there are big jumps in the transfer rates, there may be issues with buffering/congestion that is causing intermittent stalls in delivery (possibly even lost/retransmitted packets). This will definately present problems for D2. If tweaking your local network cannot smooth things out (go through the network guides in the help section), then your ISP will need to be brought on board to investigate the routes in play. If things are not moving smoothly but not "broken", you might be able to smooth things out a bit with QoS on your router. You can find out more about buffer bloating with the speedtest tool at [url=http://dslreports.com/speedtest]dslreports.com[/url]. Basically, you set the transfer rate for a particular device right at or just below your actual sustainable throughput rate. The goal is to reduce the flood of data into the buffers in an effort to reduce the idle states.