i'm in sungei wang , the streamyx connection here always give the
218.xxx ip address not matter how many times i disconnect and reconnect, maybe they give some kind of privilege to commercial building.



Tracing route to us.logon.worldofwarcraft.com [12.129.232.115]

over a maximum of 30 hops:



1 16 ms 15 ms 15 ms 219.93.218.177

2 13 ms 13 ms 13 ms 219.93.216.133

3 12 ms 12 ms 12 ms 219.93.155.29

4 13 ms 13 ms 13 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]

5 12 ms 14 ms 13 ms 210.187.142.1

6 14 ms 12 ms 13 ms vlan150-brf-sw04.tm.net.my [219.93.175.115]

7 13 ms 14 ms 13 ms 210.187.129.171

8 335 ms * 338 ms POS5-2.IG3.SAC1.ALTER.NET [157.130.210.141]

9 327 ms * * 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]

10 330 ms 333 ms 329 ms POS7-0.BR5.SAC1.ALTER.NET [152.63.52.229]

11 283 ms * 286 ms 204.255.174.178

12 293 ms 291 ms * tbr1-p013302.sffca.ip.att.net [12.122.11.217]

13 282 ms 284 ms 282 ms gbr5-p100.sffca.ip.att.net [12.122.11.74]

14 288 ms 290 ms * gar3-p360.sffca.ip.att.net [12.123.13.157]

15 293 ms * 294 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255.254]

16 281 ms 281 ms 282 ms mdf1-bi8k-1-eth-2-1.lax1.attens.net [12.129.192.250]

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.



Trace complete.

getting bad now , latency bouncing around 900 to 4000ms.
gonna back to dial-up.

same here, now also 4k++ , can't get the 218.xx and 60.xx in my area at all, no matter how many times i try, so give up and use dial-up, nice 500-900ms with very low packet loss, smooth.

Streamyx sucks , always use sub-standard solution.
The 218.xx and 60.xx, tmsuck reserved for business area, my office in Bukit Bintang always get the 218.xx and 60.xx , have not see the 219.xx b4.

was loading my char , loading seem very long this time , nm... ah i saw the green grass... oh with a blink of my eyes my char is dead... sucks 5000ms latency , quit and logout no response...heavy packet loss... shit.

what the hell , even a 56k connection can beat this kind of boardband upside down, call it boardLAG better.

25/4/05 - 1.13pm - Location Sungei Wang Plaza, with ip 60.48.37.xxx on 512k line.

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

1 14 ms 13 ms 15 ms 219.93.218.177
2 12 ms 14 ms 13 ms 219.93.216.133
3 14 ms 13 ms 13 ms 219.93.155.37
4 * * * Request timed out.
5 12 ms 14 ms 12 ms 219.93.174.83
6 305 ms 305 ms 305 ms 219.93.153.158
7 384 ms 425 ms 503 ms 12.118.44.5
8 390 ms 388 ms 387 ms 12.123.8.50
9 578 ms 546 ms 501 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
10 569 ms 425 ms 478 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
11 389 ms 398 ms 398 ms gbr6-p100.sffca.ip.att.net [12.122.11.78]
12 492 ms 489 ms 478 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
13 400 ms 399 ms 401 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255.254]
14 496 ms 497 ms 497 ms mdf1-bi8k-2-eth-1-1.lax1.attens.net [12.129.192.242]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

219.95.XX.XX seem ok this 2 night 600-1k , minimal packet loss , playable.

then use your 10 days games pass to try first lor , c the connection problem u can withstand or not.

Using Idigi and jaring , very playable , latency around 500-800ms, very minimal packet loss.

i'm also the first batch of streamyx user , can only get the 219.95.xx.xx ip , but the line is quite stable this couple days with yesterday(6/5/05) extremely good , played from 10.30pm till 4am(today) , got constant latency of 400-700++ms and the latency bar is 80% of the time stay yellow with very minimal packet loss, guess this is the best days ever since i played WOW for 2 mths.

219.95.xx.xx line is getting better nowdays , playing from 10pm till 3am , getting 80% yellow bar, very playable.

just tried ,
60.xx.xx.xx suck at 1k-1.3k(unplayable for spell caster)
219.95.xx.xx at 700-900ms( medium packet loss , unpleasant exp.)
218.111.xx.xx at 400-600ms(this very playable)

This post has been edited by arrow: May 18 2005, 03:05 PM

219.95.xx.xx going back to his old state, 1k-1.4k latency. TMSUCKs screw again.
218.111.xx.xx still ok though.
Samsung not bad using one now , although the sms side need improvement.

dunno , maybe depend on area cos at home i never get out of the 219.95.xx.xx ip range but at office i can change to 60.48xx.xx , 218.111.xx.xx, 218.208.xx.xx and 219.95.xx.xx easily just by disconnect and reconnect.

just tried , 219.95.xx.xx total screw-up , even browsing the web is a pain, using 218.208.xx.xx now , very good 300-400ms. pity i can't play long in office.

This post has been edited by arrow: May 23 2005, 06:15 PM

login just now 218.111.xx.xx very good 450 - 540ms. stable.
219.95xx.xx and 60.48.xx.xx very very lag .. 1.5- 2.5k totally unplayable.

what the @##$@# is tmnut doing... damn sian.

60.48.XX.XX and 219.95.XX.XX seem ok now - yellow bar 400-600ms , minmal lag.
yesterday around 2pm-5pm also ok below 700ms most of the time.

so what the brand and model of the modem telekom left for u to use ?

For those who stuck with 219.95.xxx.xxx ip address , there is still a way to get 400ms-900ms latency , the trick is, u must relog until u get an ip address with the third ip range is a double digit number ,that mean try get this 219.95.22.xxx , not this 219.95.333.xxx.

This also beneficial to all others ip , 218.111 / 218.208 etc.

my guildmate said that the 60.50.xx.xxx ip is good , u may start on that ,for other ip if the latency is high like 2kms, just make sure to relog until the third ip range is a 2 digit number then it will be fine.

yup ..the 219.95.xx.xxx ip , u must get it b4 midnight else u can't get it till the morning.

219.95.xx.xxx ip is becoming useless now , it started to have high ping >1.5k latency around 2 to 3 weeks ago , the latest 219.95.xxx.xxx that have good ping now is this 219.95.200++.xxx ip. Just make sure the third ip range value is >200.