I'm a wow europe player so i don't expect to get the same ping as you US players. But ping after midnight has been horrible last 2 nights.

I normally ping my ventrilo server to check how fast my wow will run as both servers are located in the same place and I find that 218.111.17-18(lower numbers are usually better for me).xx usually gives the lowest latency.

PJ, SS3 btw.

I've been travelling a lot through the ASEAN region this past few weeks and i normally get pings to my vent server of about 220-270ms (that's in Singapore, Thailand and Vietnam). So i really don't see why TM can't get their act together and give us solid latency.

Tracert shows the problem is not with my exchange but further down the route. Ie.. the bottleneck is just before the packet leaves the TMnet exchange to the foreign router.

Tracing route to xx.xx.xx.xx over a maximum of 30 hops

1 112 ms 249 ms 62 ms 219.93.218.177

2 15 ms 15 ms 15 ms 219.93.216.149

3 15 ms 13 ms 15 ms 210.187.133.83

4 15 ms 14 ms 20 ms 58.27.124.50

5 15 ms 14 ms 15 ms 219.93.174.67

6 420 ms 421 ms 421 ms 219.94.9.46

7 499 ms 497 ms 499 ms ge0-1.linx.lon.rapidswitch.com [195.66.224.207]

8 499 ms 483 ms 499 ms ge-2-24.pup.mer.lon.rapidswitch [87.117.214.6]

9 484 ms 497 ms 499 ms xx.xx.xx.xx

Trace complete.

If you want to get something done about the lag, perform tracerts and send them to streamyx. Whenever you get pings in excess of 4k, and where you get constant disconnects and lag spikes, it's pointing to lost packets. Lost packets = bad for wow.

Details on how to do the relevant tracerts can be found in the technical forums of the wow website.

A lot of the dropped packets, for me at least, are happening before it leaves routers owned by streamyx.. typically 219.94.xx.xx.

Call streamyx 1300889515 and moan to them. Get a case number after you've told them you've gone through all the usual troubleshooting BS.

Send them emails at streamyx@tm.net.my with the case number in the heading.

If i'm the only one complaining to TMnet, then they won't feel the need/pressure to do anything about it. But if more of you guys make some noise then maybe they'll actually find out what's going on and fix it.

IMO we shouldn't have to avoid slow IP addresses. There's absolutely no reason why we should accept a shoddy service from TMnet and there should be no reason why I/we should have to keep reconnecting just for a few extra ms. We pay good money for a service which is unreliable. As customers, it is within our right to complain to tmnet to ensure that the services provided by them are running properly.

It is basically your (and that is everyone who has to suffer dropped packets and high latency) duty, if the services are not up to scratch, to make a complaint to tmnet.

This is basically a call to arms. If more of us actually make some noise then maybe we'll become loud enough for tmnet to hear.

ps. When you call them tell them to shove that stupid bandwidth test up their arses as it has absolutely no impact on latency. As a gamer I would rather have a stable low latency connection then the bandwidth.

Apologies for hijacking your thread. I am not trying to be confrontational, it's just that it's very annoying to see whine posts here which do not provide any further information. As it is, it appears that, at least in my case, the traditional reliable/fast IP ranges have been acting really strangely this past week which means that a lot of the information posted in the past can now be considered out of date.

I don't think i'm asking you to do anything, I was referring to the 'tidak apa' malaysian attitude of just whining and not doing anything proactive. If anything it's a plea to them to try to find out what the cause of their problem is and to do something about it.

And since when does being female mean you're any less capable than any of the other males we have lurking in this male dominated forum?

Kudos for trying to provide a useful service on this forum but wouldn't it be nice if there was no need for a thread like this?

Same problem here, and I've lodged my complaint with tmnet. It's the last hop just before it leaves tmnet servers that's causing the lag.

See my post on http://forum.lowyat.net/topic/448637/+20

Edit: if you're too lazy to look here's what the whois query turned up on 219.93.168.250. Use this to prove that it's not your connection to your exchange but rather a problem with the routing of tmnets data traffic. You can also use it to show that the cause is not "Inter ISP connectivity"

inetnum: 219.93.168.0 - 219.93.168.255
netname: INFRA-TMNET
descr: TMNET
country: MY
admin-c: TA35-AP
tech-c: TA35-AP
mnt-by: TM-NET-AP
status: ASSIGNED NON-PORTABLE
changed: hm-changed@apnic.net 20070209
source: APNIC
changed: anieayop@tm.net.my 20050629

role: TMNET IP Administrators
address: Level 17, TM Annexe,
address: Jalan Pantai Baru,
address: 50672 Kuala Lumpur.
country: MY
phone: +603-22406120
phone: +603-22402118
fax-no: +603-22402126
e-mail: ainols@tm.com.my
trouble: abuse@tm.net.my
admin-c: AS115-AP
admin-c: SM135-AP
tech-c: AS115-AP
tech-c: SM135-AP
nic-hdl: TA35-AP
mnt-by: TM-NET-AP
changed: hm-changed@apnic.net 20070209
source: APNIC


This post has been edited by Kidicarus: Apr 28 2007, 02:02 PM

Not that strange when you consider that, those IP addresses may be what's considered their 'backbone'.

Anyway, we can conclude that it's not a 'firewall' issue.

you could kill them all with your beard ZOMG pew pew