really hope it'll be ok after this. getting tired of attack.... take bath, go dinner, come back..... then the attack hits.......

weird thing is, i got 700+ in early morning....

i think blizzard server is down

edit: its not, its streamyx

This post has been edited by keylink: Apr 3 2005, 12:34 AM

i think this issue should go to paper. It will push streamyx to get to action.

once, i did involved in telekom meeting on a big technical issue (my company was a contractor that time), their higher level people take all these poor services thing very very seriously.

the problem is (with us currently), their high level people doesn't know (i think). for them, they see that broadband bandwith is good and all is ok. they didn't know there is 1-2 sec delay, which is not really affecting surfers and downloaders, but affecting people who involve in online activity. so, the point is, to make higher level people know.

if properly written (this part i suck), the star will love this call it 'concern from online community'. maybe they will see it as minor things since it's a game, but we just need to inform them this has becoming lifestyle and big industry or evolving market, so malaysia should not be left out for something like this - just because of bad service..... just to get their attention. something like that... told ya i'm bad at writing this

just my 2 silver

take your number at the counter and wait for your turn

jk jk

yeah, hopefully we will get a solution

I don't know this is valid or not, I'm from office and we using leased line. But since mine is also 218.* so I post

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

1 1 ms 1 ms 1 ms 218.208.110.225
2 14 ms 13 ms 14 ms 218.208.68.229
3 13 ms 13 ms 13 ms 210.187.133.83
4 13 ms 13 ms 13 ms 219.93.174.83
5 307 ms 307 ms 307 ms 219.93.153.158
6 289 ms 288 ms 289 ms 12.118.44.5
7 292 ms 292 ms 291 ms 12.123.8.50
8 298 ms 296 ms 296 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
9 291 ms 293 ms 292 ms tbr1-cl2.sffca.ip.att.net [12.122.10.42]
10 289 ms 288 ms 289 ms gbr5-p100.sffca.ip.att.net [12.122.11.74]
11 286 ms 286 ms 286 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
12 299 ms 299 ms 299 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
13 295 ms 294 ms 294 ms mdf1-bi8k-1-eth-4-2.lax1.attens.net [12.129.192.
122]
14 * * * Request timed out.

And my house is at Klang area, which is quite easy to get 218.*** or 219.94.***, which both have latency less than 1k.

Dunno this helps or not

once it is 7-8 pm, it will not be possible anymore. I dont know why. So usually I connect when I arrive after work, usually before 7.

If after 7, I will hunt the 219.94.*** ip.

This post has been edited by keylink: Apr 4 2005, 05:23 PM

I will try to get setup info on my modem.... if I remember the password

If they know, I think they will. Problem is, this thing never goes up. For call centre, our call is just a call from somebody that have slow connection. That's all they know. Solution? Reset your modem / pc /etc
or :
'we have problem with <insert the value you told him either 219 218 whatever>,
please be patient / try reconnect later etc' - hang up - close call.....

As long as this thing is not escalated to their technical team (I mean the 'technical' team, not the 'so called technical' call centre people), no one will notice.

If I have the means, I will just make 10-20 of same reports, record their response (which WILL be all different) then publish to paper. At least we can prove their call center super suck.

oh well, i hope solution to this new problem will somehow resolve the old problem as well............ hopefully.................. dream on............................................

Hmm, i think this is not Streamyx only issue.... Jaring also facing same problem...

taken from their site:

Slow Access/Browsing to International sites.

[English Version]

1. This announcement is addressed to all JARING Members.

2. We would like to inform you of a slow browsing speeds when attempting to access the international sites which started at 6:20 am on April 7, 2005.

3. Users may experience slow access/browsing performance, however sending/receiving e-mail to/from overseas will not be affected.

4. We are still working towards rectifying the problem. We will keep you posted as we get these matters resolved.

5. We apologize for any inconvenience caused.

6. Thank you.


JARING Network Operation Center

you so funny aa.. what you eat today aa??

how about this? before it shot up 6k

hope tomorrow will be better



This post has been edited by keylink: Apr 9 2005, 01:48 AM

i think no difference in ip assign between 512k and 1Mb. Anyway, place maybe a factor, since I have 1 guild member can't get 219 at all. Weird huh... we all crying for 218 and 60, and this guy never get anything other than 218 and 60.

edit: and I usually can get 219.94, and 218 if only before 7-8 pm. never see 60

This post has been edited by keylink: Apr 11 2005, 12:44 PM

what sampan?? they use boat that connect Auberdine and Methenil Bay... if you don't believe me, ask the people at Auberdine docks......

btw, repair is slow because they dun have underwater breathing spell / item......

don't press that!!! it will cause the omega murloc to come here and kill us.... since we are OT now

back to the topic:

since connection can be said restored, maybe we can start monitoring how is 219.95.* now.

eh, i though 219.93.* is server? correct me if i'm wrong. never get that one

wah... bentong gangster also play WOW aa?

hmm... that...... might..... be hard to happen
try bring the cd install there

anyway, i'm still puzzled why some ppl is smooth and some got lag spike etc (this maybe due to 20th repair haven't done though)

and why some ppl can get certain ip while some cannot... is it area? node? config? or something?

watch out, got high sea pirate nowadays.......

later, 'repair delayed because repair ship was hijacked'

i'm still surviving 219.94.*

other than that, hopeless.

with this ip, i got around 800 at most, normally stay at 500-600 range. didn't seem to have any lag or lag spike.