---

xicoboom wrote:

...

9 269 ms 28 ms 33 ms 12.81.8.69
10 64 ms 81 ms 40 ms 74.175.192.190
11 218 ms 248 ms 278 ms cr81.fldfl.ip.att.net [12.122.106.94]
12 154 ms 100 ms 151 ms cr2.ormfl.ip.att.net [12.122.1.45]
13 317 ms 370 ms 286 ms cr1.ormfl.ip.att.net [12.122.5.185]

....

---

Hard to tell with just one tracert, but it appears that your ping times increase pretty substantially as you leave hops 9 and 10 and go to hops 11 et seq (though 12 isn't all that bad).  It looks like a congestion issue in what appears to me to be the Orlanda, FL area.  One thing I have done in the past is to set up continuous pings ("-t") for two or three nodes along the way and watch for a few minutes to make sure the jump point is consistant.

If this hasn't already gone away, then I'd have to recommend you click the Customer Service link to send a Private Message (PM) to the AT&T customer service team to look in to this problem. As before, you can expect a reply via return PM (the blue envelope in the upper right hand corner of this site).  Send them a link to this thread, etc.

Well it seems that today a tracert shows a good ping for AT&T. Did 3 different tracert and it's almost always the same ping times. Could it be possible that AT&T was doing some work at the hops where i was starting to lag?

C:\Windows\System32>tracert game.lemonmc.com

Tracing route to game.lemonmc.com [216.155.140.110]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.1.254
2 29 ms 28 ms 23 ms 108-84-116-3.lightspeed.wepbfl.sbcglobal.net [10
8.84.116.3]
3 38 ms * * 99.128.141.36
4 * * * Request timed out.
5 * * * Request timed out.
6 26 ms 26 ms 25 ms 70.159.202.194
7 29 ms 27 ms 27 ms 12.81.20.72
8 28 ms 27 ms 28 ms 12.83.6.122
9 26 ms 26 ms 27 ms 12.81.8.69
10 33 ms 32 ms 33 ms 74.175.192.190
11 64 ms 64 ms 64 ms cr81.fldfl.ip.att.net [12.122.106.94]
12 63 ms 63 ms 63 ms cr2.ormfl.ip.att.net [12.122.1.45]
13 62 ms 63 ms 63 ms cr1.ormfl.ip.att.net [12.122.5.185]
14 64 ms 67 ms 66 ms cr2.hs1tx.ip.att.net [12.122.1.5]
15 65 ms 63 ms 66 ms cr1.dlstx.ip.att.net [12.122.28.157]
16 61 ms 61 ms 61 ms dlstx02jt.ip.att.net [12.122.214.245]
17 64 ms 70 ms 71 ms 192.205.36.94
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 87 ms 83 ms 84 ms ve66-br2.pnj1.choopa.net [108.61.93.105]
22 85 ms 83 ms 84 ms ve105-as1.pnj1.choopa.net [108.61.79.86]
23 83 ms 82 ms 82 ms 216.155.140.110.choopa.net [216.155.140.110]

Trace complete.

---

xicoboom wrote:

Well it seems that today a tracert shows a good ping for AT&T. Did 3 different tracert and it's almost always the same ping times. Could it be possible that AT&T was doing some work at the hops where i was starting to lag?

....

---

That, or some dynamic routing rules caused a bad situation, or there was a DoS attack against some component of AT&T's network or something hosted in that area, or a bunch of compromised PC's using AT&T in your area were participating in a DDoS attack against a site far away.

The possibilities are endless.  I'm just glad your problem went away.