Thanks for your reports, all. We're going to look into what's going on, but you can help us out by getting us some traceroute data and posting it here. I'm going to copy/paste some instructions from a while back regarding how to collect this:
You can access traceroute through the Command Prompt. Click the Start Menu and type "cmd" or "command". When the shell opens and you are presented a prompt, type one of the following:
If you play on an East Coast server: tracert 159.153.92.28
If you play on a West Coast server: tracert 159.153.68.252
If you play on a European server: tracert 159.153.72.252
When providing the traceroute output, if you are worried about providing information regarding your public IP address, remove any lines up to and include your public IP by replacing them with ***.
Here's what we're looking for as an example:
Tracing route to 159.153.92.28 over a maximum of 30 hops
1 1 ms 1 ms 1 ms ***
2 1 ms 1 ms 1 ms aus-brdr-01.twtelecom.net [207.114.255.13]
3 68 ms 39 ms 40 ms ash1-pr1-xe-0-3-0-0.us.twtelecom.net [66.192.240.218]
4 42 ms 42 ms 42 ms 64.125.199.186.t00673-01.above.net [64.125.199.186]
5 42 ms 43 ms 42 ms 159.153.92.28
Trace complete.
Other additional information that will help us as we investigate this: your ISP and your City/State.
Thanks!
:
Are you getting DC'd back to the Server Selection?
:
Thanks for all the information! I've passed it along and we're actively looking into what is going on.
