Recently i have this problem.
I logged in with a decent latency of 250-400ms but the latency keeps rising until it is unplayable.
I had to reset modem many times to get a decent IP that doesnt lags out.

Another problem, my latency always hits above 600ms around 11am-12am.
Everyday TEPAT TEPAT 11am, i will DC then i have to reconnect and stuck in 600ms+.
Its as if that the clocktower hits 12 for Cinderella to return home.

try get d ip range of 60.x.x.x
line for tis ip range is better as from my experience

why is streamyx so strange one? my friend and I subscribe to 1 meg package but i am in ampang and he in damansara. i get 60 percent when i do speed test, he get 80percent!!!! No fair ...

its time for a new govt

streamyx is never consistent. even jaring is better

approving this thread.

on day slow like hell. i heard they throttling EVERYTHING (even http).

me too experienced this....even I have SSH access to do tunneling into one of my server in Jaring datacenter..........the ping reply circa 800-900.....12am is bed time btw

Agreed. Bad ping = dead during raids

lolx..streamyx always sot sot de..

Crap latency atm

the bar have been red all the time for me now .

This post has been edited by nagflar: Aug 23 2008, 01:23 PM

Darn...today my latency unstable...sometime lag sometime smooth, dunno how play.

I cant take this anymore.

The latency not playable at all.

900-1.2k ms atm.
hail tmnet.

heh (off-topic) I see joeboto, do you still remember me dude? hehe

482 1PM

setapak
i cant play cs 1.6
ping 100++
sometime 300++
until midnight 1am just back to normal
haizz

MCB.

I wanna punch streamyx already.

Ran ZA for like a gazillion times.
Berserker's call finally dropped just now n i f***ing DC.
Druid rolled it. GG.

berserker call

pain man

Hi Guys,

Just want to share what I have. I made tracert result to WoW Realm and then forward the result to Teleglobe.net support personnel.

They replied and mentioning that I should talk to TMNET to have better load balancing. Maybe we all can try this, and send the feedback to TMNET 2nd line support to request for improvement.

This is the tool that i use to make Trace Route to WoW Realm : http://winmtr.sourceforge.net/


==============================================

Hi,

It appears that one of TM NET interface with us is saturating while the other
is not. TM NET should be able to better load balance their traffic with us
to provide a better customer experience.

Best regards,

Charles.

> Hi Support,
>
> I am World of Warcraft online game player from Malaysia and recently I been un-pleased with high latency in game
>
> Following is my Trace Route Result and the bottleneck start from Teleglobe.net which hop number 12.
>
> Please do something to improve the network else we are suffer at here. I been contacting my broadband Internet ISP which is TM NET (or Telekom Malaysia) and according to their finding, the problem start from Global Internet line.
>
> Based on the result, I believe you can clearly see that the slow ping start from HOP 12 which is "12. hop: 216.6.84.49 (if-13-0-0.mcore3.LAA-LosAngeles.teleglobe.net): 291 ms"
>
>
>
> Host information for "12-129-225-14.attens.net":
> Host name: 12-129-225-14.attens.net
> IP address: 12.129.225.14
> Country: US (UNITED STATES)
>
> Trace route to "12.129.225.14" over a maximum of 30 hops:
>
> 1. hop: 192.168.1.1 (login.router): 0 ms
> 2. hop: 219.93.218.177: 13 ms
> 3. hop: 219.93.219.21: 7 ms
> 4. hop: 58.27.103.73: 7 ms
> 5. hop: 58.27.103.66: 7 ms
> 6. hop: 58.27.103.106: 7 ms
> 7. hop: 210.187.142.5: 8 ms
> 8. hop: 203.106.240.202: 8 ms
> 9. hop: 58.27.113.30: 166 ms
> 10. hop: 58.27.124.58: 8 ms
> 11. hop: 219.93.174.84: 8 ms
> 12. hop: 216.6.84.49 (if-13-0-0.mcore3.LAA-LosAngeles.teleglobe.net): 291 ms
> 13. hop: 216.6.84.114 (Vlan42.icore1.LAA-LosAngeles.teleglobe.net): 291 ms
> 14. hop: 192.205.35.129: 292 ms
> 15. hop: 12.122.90.66 (tbr2.la2ca.ip.att.net): 293 ms
> 16. hop: 12.127.3.189: 215 ms
> 17. hop: 12.122.255.74: 216 ms
> 18. hop: 12.129.193.242 (mdf001c7613r0003-gig-10-1.lax1.attens.net): 215 ms
> 19. hop: 12.129.209.99: 214 ms
> 20. hop: timed out.
> 21. hop: 12.129.225.14 (12-129-225-14.attens.net): 294 ms

============================================