i always get constant 400ms on my 124.82 streamyx IP during the day and it goes 350ms after 2am. but this pass 1 week i am getting like 1000ms. weird. anybody know what is wrong?

ok. its not tm.net problem. its AT&T. check out the trace result. it spike at at&t nodes. one malaysian dude complain at bliz tech support and his trace is also similar to mine.

http://forums.worldofwarcraft.com/thread.h...=82083455&sid=1

btw, this is my trace result.

C:\Documents and Settings\nitrofang>tracert 12.129.225.82

Tracing route to 12-129-225-82.attens.net [12.129.225.82]
over a maximum of 30 hops:

1 58 ms 62 ms 46 ms 219.93.218.177
2 19 ms 30 ms 31 ms 219.93.216.165
3 30 ms 30 ms 30 ms 210.187.132.83
4 46 ms 30 ms 15 ms 58.27.124.58
5 30 ms 15 ms 46 ms 219.94.9.25
6 437 ms 406 ms 405 ms 12.118.124.93 <--------this is the culprit
7 484 ms 484 ms 515 ms tbr1-p012101.la2ca.ip.att.net [12.122.2.250]
8 421 ms 421 ms 452 ms 12.127.3.185
9 453 ms 452 ms 436 ms 12.122.255.74
10 419 ms 406 ms 405 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed
Trace complete.

C:\Documents and Settings\nitrofang>

This post has been edited by nitrofang: Mar 18 2007, 05:41 PM

FYI, blizzard use AT&T services for wow.

this is reply from one of the blue in bliz forum.

Hello all,

It seems like the problem is resolved for most players but since there are still a few, we will create a sticky to help consolidate the information.

Thus far most traces collected appear to be having problems nearing AT&T's routers:
14 * att.sjc03.atlas.cogentco.com (154.54.11.238) 254.117 ms 295.352 ms

refer thread http://forums.worldofwarcraft.com/thread.h...&sid=1&pageNo=7

and yes. the problem is actually faced not only by malaysians, but from also from australia, philipines, south and east US.