View Single Post
Career Officer
Join Date: Jun 2012
Posts: 1,116
# 6
10-13-2013, 07:08 PM
I also have AT&T U-verse (in the Milwaukee, WI area) and am having the same issue now. The launcher will take my password, but then stalls when checking the patch server.

Earlier this afternoon I was able to log in, but was experiencing severe rubberbanding.

Here are my ping results:

Quote:
Pinging patchserver.crypticstudios.com [208.95.185.41] with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=95ms TTL=49
Reply from 208.95.185.41: bytes=32 time=92ms TTL=49
Request timed out.
Reply from 208.95.185.41: bytes=32 time=85ms TTL=49
Reply from 208.95.185.41: bytes=32 time=85ms TTL=49
Reply from 208.95.185.41: bytes=32 time=89ms TTL=49
Reply from 208.95.185.41: bytes=32 time=88ms TTL=49
Request timed out.
Reply from 208.95.185.41: bytes=32 time=88ms TTL=49
Reply from 208.95.185.41: bytes=32 time=81ms TTL=49
Reply from 208.95.185.41: bytes=32 time=80ms TTL=49
Reply from 208.95.185.41: bytes=32 time=87ms TTL=49
Reply from 208.95.185.41: bytes=32 time=86ms TTL=49
Reply from 208.95.185.41: bytes=32 time=91ms TTL=49
Request timed out.
Reply from 208.95.185.41: bytes=32 time=89ms TTL=49
Request timed out.
Reply from 208.95.185.41: bytes=32 time=87ms TTL=49
Reply from 208.95.185.41: bytes=32 time=88ms TTL=49
Request timed out.
Reply from 208.95.185.41: bytes=32 time=81ms TTL=49
Reply from 208.95.185.41: bytes=32 time=84ms TTL=49
Request timed out.
Reply from 208.95.185.41: bytes=32 time=92ms TTL=49
Reply from 208.95.185.41: bytes=32 time=89ms TTL=49

Ping statistics for 208.95.185.41:
Packets: Sent = 25, Received = 19, Lost = 6 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 95ms, Average = 87ms
...and my tracert results:

Quote:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms homeportal [192.168.1.254]
2 56 ms 24 ms 25 ms 99-122-68-3.lightspeed.milwwi.sbcglobal.net [99.122.68.3]
3 * * * Request timed out.
4 26 ms 24 ms 27 ms 12.83.79.141
5 49 ms 50 ms 51 ms cgcil02jt.ip.att.net [12.122.81.21]
6 98 ms 92 ms 91 ms be2000.ccr21.ord03.atlas.cogentco.com [154.54.12.85]
7 101 ms 95 ms * be2004.mpd22.ord01.atlas.cogentco.com [154.54.5.9]
8 * * 93 ms be2140.ccr22.bos01.atlas.cogentco.com [154.54.43.186]
9 116 ms 115 ms 100 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42]
10 92 ms * 89 ms 38.111.40.114
11 86 ms * * 208.95.185.41
12 * 91 ms * 208.95.185.41
13 * * 91 ms 208.95.185.41

Trace complete.
Most worrisome of all, nettest wouldn't even run - it timed out almost immediately after launch.

Update: Late Sunday night, I was able to log in and work in the Foundry with no issues. Hopefully that means whatever bottleneck was causing the connection issues has gone away.

Last edited by paxfederatica; 10-13-2013 at 10:01 PM.