If we had a decent ISP, we shouldn't even need to think of this. But being that we're dealing with politicians with wallets in their minds, this is the solution to satisfy their greed.

Yeah..add 20-40 ringgit more for the Gaming Package.

Alternatively, get investors to buy Malaysia out. Quality is long overdue in this country.

And it'll get oversubscribed and we'll be back to square one. hehehe

what bout 56k.. still the same madness?

Ok with all the rants going on (hehe)
Is there someone out there actually able to play WoW without any troubles?
If there is someone out there that could at this moment...
Would you please share your little secret?
Thanks in advance.

Well there will be a World of Warcraft Boardgame coming out by the end of this year. I guess those hardcore can get one of these just in case something like this happends again, they can still play WoW.

Well, just read this on the broadband forums on LYN itslef. here's the link to that thread for those too lazy to go there themselves

http://forum.lowyat.net/index.php?showtopic=144843

Anyway...


This may be the problem thats affected the 219.xx.xx.xx IP for the past 3 weeks. Hopefully this will solve the high latency some people have been seeing.


This should be the recent problem that has everyone complaining. Things should be looking up soon then.

Good luck to everyone. Keep your fingers crossed and you'll still have your Sunday WoW maraton (You know you do! Don't hide)

so tomorrow wat should i do? any suggestion?

tomorrow ah? start crying to tm "F" net and beg them for some miricle!

Lol i win you alot. see my latency

This post has been edited by jimmy79: Apr 8 2005, 11:17 PM


Attached File(s)
 lag.bmp ( 576.05k ) Number of downloads: 23

Strange... when I entered just now, it was VERY fast. Almost back to normal but hung right after loading. Then I tried again, and managed to enter with 5k ping. *sigh*

EDIT: Wah Wah...500ms and counting!

EDIT2: Stablized at 1134ms! Sweet! Play time!

EDIT3: Dratz...the connection is very unstable...it states there 2400ms now, but the response is like 700-1500ms with periodic lag spikes.

This post has been edited by Wolfgard: Apr 9 2005, 12:33 AM

ok connected to 219.93.xxx.xxx

in game ping shown is 3k. but im getting fast response sometimes. its fast and slow fast and slow. Very unstable.

It's back up to 4k again. False hope...sheesh. Sometimes fast (normal speed, can cast instantaneously) and mostly laggy.

EDIT: Response can be very very unpredictable. I dare not leave the UC in case everything goes back to 10k while I'm stuck outside not getting the rest bonuses.

This post has been edited by Wolfgard: Apr 9 2005, 12:43 AM

using 219.95 ip:
Pinging 12.118.44.5 with 32 bytes of data:

Reply from 12.118.44.5: bytes=32 time=398ms TTL=240
Request timed out.
Reply from 12.118.44.5: bytes=32 time=358ms TTL=240
Reply from 12.118.44.5: bytes=32 time=343ms TTL=240
Reply from 12.118.44.5: bytes=32 time=359ms TTL=240
Request timed out.
Reply from 12.118.44.5: bytes=32 time=359ms TTL=240
Reply from 12.118.44.5: bytes=32 time=359ms TTL=240
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 12.118.44.5: bytes=32 time=360ms TTL=240
Request timed out.
Reply from 12.118.44.5: bytes=32 time=373ms TTL=240
Reply from 12.118.44.5: bytes=32 time=358ms TTL=240
Reply from 12.118.44.5: bytes=32 time=391ms TTL=240
Reply from 12.118.44.5: bytes=32 time=377ms TTL=240
Request timed out.
Reply from 12.118.44.5: bytes=32 time=357ms TTL=240
Request timed out.
Request timed out.
Reply from 12.118.44.5: bytes=32 time=357ms TTL=240
Reply from 12.118.44.5: bytes=32 time=359ms TTL=240


350+ ping to the server, but times out intermittently.

I dont have any idea too

I'm running on 219.95 too. Yes, it's shifts from fast to slow and back again. I'm not sure I should be happy or angry now...considering I can actually play decently. But, I'll stay in game for awhile more just to check on the lag rate:

My rough estimate of ping rate based on in game response:
Fast: about 500-700ms
Slow: varies from 2000ms to 6000ms.

Average based on latency meter: varies from 2500-4500ms. Strange huh?

keep getting better now

Tracing route to us.logon.worldofwarcraft.com [12.129.232.116]
over a maximum of 30 hops:

1 * * * Request timed out.
2 21 ms 21 ms 22 ms 219.93.218.177
3 23 ms 21 ms 19 ms 219.93.216.109
4 20 ms 35 ms 21 ms 219.93.155.33
5 20 ms 43 ms 22 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
6 20 ms 20 ms 18 ms 210.187.142.1
7 18 ms 19 ms 20 ms vlan150-brf-sw04.tm.net.my [219.93.175.115]
8 38 ms 20 ms 20 ms 210.187.129.171
9 279 ms 280 ms 280 ms POS5-2.IG3.SAC1.ALTER.NET [157.130.210.141]
10 * 286 ms 286 ms 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]
11 295 ms 292 ms * POS7-0.BR5.SAC1.ALTER.NET [152.63.52.229]
12 240 ms 238 ms 239 ms 204.255.174.174
13 * * * Request timed out.
14 246 ms * * gbr5-p100.sffca.ip.att.net [12.122.11.74]
15 248 ms 247 ms 246 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
16 * 256 ms 251 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
17 249 ms * * mdf1-bi8k-2-eth-1-3.lax1.attens.net [12.129.192.
110]
18 * * * Request timed out.
19 * * ^C

Looking good! That means the problem we were experiencing for the last 3 weeks is indeed related to the current one. Still, in game latency is hovering at 4k.

Haha Wolf, im experiencing exactly the same thing. Got invited to Sunken Temple, latency shoots up to 8k. Cant play. Relog hearth back to Orgy quit. At least we know that they are somehow fixing it, and its a good sign. 219 might get back to normal.

From 218

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 22 ms 22 ms 219.93.218.177
3 21 ms 20 ms 21 ms 219.93.216.117
4 20 ms 20 ms 20 ms 219.93.155.37
5 21 ms 20 ms 22 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
6 22 ms 21 ms 21 ms 210.187.142.1
7 20 ms 22 ms 35 ms vlan150-brf-sw03.tm.net.my [219.93.175.114]
8 20 ms 22 ms 21 ms brf-backbone02-ether0-0.tm.net.my [202.188.0.8]

9 * * 867 ms POS5-1.IG3.SAC1.ALTER.NET [157.130.214.117]
10 870 ms 866 ms * 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]
11 * 861 ms 861 ms POS7-0.BR5.SAC1.ALTER.NET [152.63.52.229]
12 878 ms * 878 ms 204.255.174.178
13 867 ms 864 ms 871 ms tbr1-p013302.sffca.ip.att.net [12.122.11.217]
14 863 ms 867 ms 859 ms gbr5-p100.sffca.ip.att.net [12.122.11.74]
15 870 ms 868 ms 865 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
16 873 ms 875 ms 882 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
17 872 ms 880 ms 875 ms mdf1-bi8k-2-eth-1-3.lax1.attens.net [12.129.192.
110]
18 * ^C

From 219

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 22 ms 23 ms 22 ms 219.93.218.177
3 20 ms 20 ms 20 ms 219.93.216.125
4 20 ms 21 ms 21 ms 219.93.155.33
5 22 ms 21 ms 21 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
6 21 ms 20 ms 21 ms 210.187.142.1
7 22 ms 21 ms 21 ms vlan150-brf-sw04.tm.net.my [219.93.175.115]
8 20 ms 21 ms 21 ms 210.187.129.171
9 297 ms * * POS5-2.IG3.SAC1.ALTER.NET [157.130.210.141]
10 295 ms * 295 ms 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]
11 289 ms 291 ms 290 ms POS7-0.BR5.SAC1.ALTER.NET [152.63.52.229]
12 * 249 ms 248 ms 204.255.174.178
13 250 ms 251 ms 247 ms tbr2-p013802.sffca.ip.att.net [12.122.11.229]
14 249 ms 247 ms * gbr5-p20.sffca.ip.att.net [12.122.11.90]
15 241 ms * * gar3-p360.sffca.ip.att.net [12.123.13.157]
16 256 ms * 256 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
17 * * * Request timed out.
18 * ^C


I wouldn't get my hopes up just yet. The above demonstrates TMnet realising that they can get less complaints from people who did not check latest news. And the fact that they dumped most people on 219s, their temp solution is to throttle the bandwidth for the majority's benefit.

Lets not forget these servers are temporary routers and we're pinging at 1:00 AM in the morning on a Friday night. During the day, it should be completely different story.

It only makes sense to pass judgement when they officially announce they've completely (and supposedly) nailed the current issues.

Yeah I'm getting lots of packet loss on 219.95.xxx. I can go around harvesting herbs tho. Just have to tahan the intermittent periods of 'time outs'

93 and 94 are still unplayable (2k+ ping). If you want to at least browse/play AH, reconnect until you get 95.


1 * * * Request timed out.
2 24 ms 23 ms 23 ms 219.93.218.177
3 22 ms 21 ms 23 ms 219.93.216.189
4 23 ms 21 ms 27 ms 210.187.143.5
5 86 ms 215 ms 198 ms 210.187.142.1
6 23 ms 23 ms 23 ms vlan150-brf-sw03.tm.net.my [219.93.175.114]
7 22 ms 21 ms 23 ms brf-backbone02-ether0-0.tm.net.my [202.188.0.8]

8 * 282 ms 283 ms POS2-2.IG3.SAC1.ALTER.NET [157.130.210.145]
9 283 ms * 282 ms 0.so-0-1-0.XR1.SAC1.ALTER.NET [152.63.54.122]
10 * 280 ms * POS6-0.BR5.SAC1.ALTER.NET [152.63.52.225]
11 241 ms * 242 ms 204.255.174.174
12 * 243 ms 239 ms tbr2-p013202.sffca.ip.att.net [12.123.13.70]
13 248 ms * 248 ms 12.122.11.94
14 240 ms 241 ms 243 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
15 252 ms 250 ms 249 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
16 249 ms 250 ms * mdf1-bi8k-1-eth-2-3.lax1.attens.net [12.129.192.
126]
17 * * * Request timed out.