I notice that connection to various server also matters. Not sure what that means.

Tested on 18th May 2007.

Bandar Seri Damansara
219.95.x.x = Bad > latency above 2k
60.48.x.x= latency between 800ms to 1400ms
60.51.x.x= superb. average 350 - 520ms
124.82.xxx = avr 600ms to 1200ms

Having said that, my connection on 60.51.xx.xx usually gives me 350 - 520ms connected to Gorgonash server, to Proudmoore, i get 700 to 1k ms.

Related?

218.111.* has high packet loss, tho tmnet doesn't seem to realize it.
60.49.* PoS
60.50.8 PoS
60.51.* Was ok, these days its not that good.
60.52.* PoS
60.53 Was ok as well, tho hard to get on it now.

Contacted tmnet for the past couple of weeks, explaining to them the situation, providing numerous traceroutes and stats. Gist of it was telling me to shag myself and/or contact [upstream x] and file a complaint. I guess as customers, we have jack rights and if theres a problem, we have to run around the globe and sort it for them.

Unfortunately, they do not seem to realize, international saturation on their routing paths is *their* problem, not ours. The simple fact that some ip ranges have less traffic congestion than others, and the fact that almost all their upstream providers are getting congested means they need to look at their routing and also lease more upstream to ease congestion on international traffic.

Sadly I think the problem is not only congestion, but its complicated with incompetancy on their part, poor maintenance, terrible routing and annoying customer service.

If it is indeed our problem, then lets take it to heart and flood them with complaint emails, calls and let them see the light. Please, lets truely make it our problem and start helping them sort it out. Whatever shitty ip range you are one, take a traceroute, pick some major upstreams that are with tmnet as well, and take traceroutes on those as well (very good chance its shitty as well), and submit it enmasse.

Some upstream providers:
1) www.nac.net
2) www.teleglobe.net
3) www.att.net (what wow servers mainly use)
4) www.opentransit.net

AFAIK a good majority of our int traffic goes through these providers, and we are pretty much shit out of luck going through 'em. We had another upstream provider, alter.net which was ok sometimes, but tmnet does not seem to use it anymore or cut its lease with 'em. Why are these monkeys removing upstreams and now I hear we've got 4mb packages......

any fellow wow-ers staying at farlim know any good ips? i might need some help here

Ipoh Road

218.208.X.X = Best. 200-400ms whole day.
218.111.X.X = High packet loss.
219.95.X.X = Worst.
219.95.2XX.X = High latency (400-800ms) but no packet loss hence no lag spikes in game.

Why not complain straight to the MCMC?

coz they probably have a huge flood of complaints that they probably don't know how or where to start.

and i can imagine them just presenting the case to the ISP and waiting for the ISP to do something so can you imagine TMNet doing something about it? don't think so.

219.94 is still the best for Setapak. Currently playing around 300-700ms on Illidan. It lagged for an hour or 2 and now it's back to normal.

Edit: Lag mode ON at 9.30pm. 800-1500ms atm

This post has been edited by TristanX: Jun 4 2007, 09:34 PM

60.49.xxx.xxx best for my area, Wangsa Maju s4. 218.208.xxx.xxx is comparable to 60.49 but experience short lag spikes sometimes in game. Other IPs are terrible, lags and delays over 1-2 seconds.

Sabah - Kota Kinabalu

60.53.x.x is the only playable IP, but quality varies widely. 300-400ms on good days, 400-700ms is normal, 700-1100ms on bad days.

60.50.x.x typically 1100ms and way above.

124.x.x.x also typically 1100ms and way above.

My line quality may have something to do with it, have heard from friends here who consistently get 200ms on 60.53.x.x I'll believe it when I see it though.

omg..i asked tmnsts whats with all the lags nowdays and they said "belapa hali ini,line sangat teruk"
WTF? everyday also lag line with tmnuts ler

218.XXX.XXX.XXX--->lag spikes

IPs that went bad recently
60.48.XXX.XXX
60.49.XXX.XXX
60.50.XXX.XXX
60.51.XXX.XXX
60.52.XXX.XXX
60.53.XXX.XXX<---cant get in my area

btw im staying in Farlim,Penang.Any idea of good ips from this area...need help here? struggling to play wow bad!

@.@ G fking G!

I can't play @ BG now, 3K lag using 218 ip...so I'm join the AV afk cavers

well i m staying in free school, penang and 60.49 works for me recently.. getting range from 400-800 ms... u should try on that, since farlim is like 10 minutes away from my place. btw, i usually play from 8pm to 3 am and full time on weekends

well as from the info i get...although u stayed 10mins away from me but we are in diff area....i think we are using the diff hub to connect...but anyhow ill try ;p thanks

arghh... damn.. Me in BM and office in d island... both also fcking lag these week.. yesterday was the worst.... 10k~20k ms and damn every 10mins the fcking ADSL light blinking..........

anyone in PG having the same problem like me?

*sry very frustrating.. dc every 10mins

go to play ice internet cafe in farlim then.. the average ping there is around 600 - 800ms... the owner there is my former guildmate and now he is setting up a guild in thaurissan name eclipse... quite a lot of wow kaki playing there...
sometime i go there and play with my frens too...

Seremban:

60.53.X.X - totally unplayable... average 1.8k ms or above. Enjoy more DCs!!!
60.51.X.X - lag... still playble(soloable, no raid). average 800+ ms.
218.111.X.X - good ip!!! 5XX - 7XX ms. Man, this is really HARD for me to get this ip class in my place.

Another thing, I found out that I can get average 3XX ms(60.51.X.X) in early morning. Must be TMnutz bandwidth problems.

Any of u tried configuring ur MaxMTU and RWIN to see if it affects latency?

LYN n00b question : what is MaxMTU and RWIN? And how to check if it affects latency?

BTW guys, have any of you noticed the Low Latency that we're getting in a lot of the instances, areas, etc.? http://forums.worldofwarcraft.com/thread.h...&sid=1&pageNo=1 . Looks like Blizz is not even sure what is going on and all that they had to say is "If this is happening to you during patch 2.1.1, what's oging to happen post-patch-2.1.2?" Fulamak.

This post has been edited by myremi: Jun 8 2007, 11:33 AM