Let's try and compile as much technical data on the issue as possible to help both our ISPs and SE figure out what is happening here.
I'm working with AT&T on this at the moment as well, but I've noticed that once my queue pops and I enter whatever it is I'm doing, the latency to the server skyrockets. For example, I average ~55ms to the Malboro Server (199.91.189.24). I setup a continuous ping to the server and can see the latency is fine and I'm not experiencing any lag. As soon as my queue for trial roulette pops, the latency nearly doubles. At it's worst, I've seen it over 200ms
Code:
Fri Oct 3 19:21:18 EDT 2014 | 64 bytes from 199.91.189.24: icmp_seq=1 ttl=239 time=294 ms
Fri Oct 3 19:21:20 EDT 2014 | 64 bytes from 199.91.189.24: icmp_seq=1 ttl=239 time=93.2 ms
Fri Oct 3 19:21:21 EDT 2014 | 64 bytes from 199.91.189.24: icmp_seq=1 ttl=239 time=223 ms
It could be coincidence, but it seems almost like a trigger with how the latency and the queue popped at the same time. Yesterday the latency kicked in around 6:55pm EST on it's own - same time as listed above.
Unless AT&T is doing some QoS Traffic shaping, this seems a bit odd. Is there some other way I should be testing the latency? Are there different servers for the primal instances and such? I know many people have complained of this lag since the latest patch, but I've only just seen this behavior after the patch and after upgrading from their DSL 6Mbp/s line to the 18 Mbp/s U-Verse line. The same medium is used, so it seems likee more of a traffic shaping or routing issue.
Code:
docfiord@desktop:~$ tracepath -n 199.91.189.24
1: 192.168.1.103 0.108ms pmtu 1500
1: 192.168.1.254 1.026ms
1: 192.168.1.254 0.895ms
2: External Next Hop 26.261ms
3: 76.201.208.74 25.545ms
4: 76.201.208.125 25.665ms
5: 12.83.82.145 27.000ms
6: 12.122.141.233 29.426ms asymm 7
7: no reply
8: no reply
9: no reply
10: no reply
11: no reply
12: 4.69.134.70 53.181ms asymm 16
13: no reply
14: 4.69.141.5 140.592ms asymm 13
15: 4.69.141.1 53.807ms asymm 14
16: 4.59.178.74 53.472ms asymm 15
17: no reply
18: 192.34.76.2 59.605ms asymm 14
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
*EDIT*
To help with the troubleshooting, try to get a ping sample and a traceroute to your server from both when it is working fine and when there is lag. Here's how you can do it. If you are on a PS3 or PS4, doing this from your PC will still provide a semi-accurate reading as both devices are rpesumably using the same gateway.
Server IP addresses can be found from http://www.arrstatus.com/ by changing the Display Mode to IP Address. Copy and paste the reults from each test below.
PING
Windows XP : Start > Run > Type "cmd" (without the "") and press ENTER. Type "ping x.x.x.x" (substitue x.x.x.x for your server's actual IP address)
Windows 7: Start > Type "cmd" (without the "") and press ENTER. Type "ping x.x.x.x" (substitue x.x.x.x for your server's actual IP address)
TRACEROUTE
Windows XP : Start > Run > Type "cmd" (without the "") and press ENTER. Type "traceroute x.x.x.x" (substitue x.x.x.x for your server's actual IP address)
Windows 7: Start > Type "cmd" (without the "") and press ENTER. Type "traceroute x.x.x.x" (substitue x.x.x.x for your server's actual IP address)