I have a D-Link DSL-300G. Is there a faster way than the on/off switch to reboot the modem to try and get the 218.* range of IPs.. maybe from the Web control panel?

Simply disconnecting and reconnecting the connection only seems to keep me stuck in the 219.* range.

But still not entirely Blizz's fault...

the 2.5k to 3k latencies can be put down to Streamyz trans-pacific lag + Blizz lag.

It's always 700+ or so in the early morning during the workweek... then everybody and their next door neighbour wakes, fires up their internet connection (at work and at home) and then everything goes south.

I had a lot of adventuring time during the weekend playing from 2am to 7am in the middle of the night.

I've heard some rumours that the latency has finally cleared up now, with people getting 700ms latencies and below even when on 219.* IPs.

Anyone hear want to confirm or deny this?

EDIT - Still at work, can't check myself.


This post has been edited by wildside: Mar 29 2005, 02:27 PM

Dear Malaysian World of Warcraft Gamer,

We are not aware of any support by Blizzard Entertainment to allow Malaysians to play World of Warcraft.

As such, we are not obliged to provide any assistance to you in any way, shape or form.

In other words, sux to be j00!!

Well, it's not much, but it's encouraging.

Here's to the latency improving as the day goes on, and the servers up when I get home from work.

Gone through way too many evenings without WoW now.

'We dun believe j00!!!111ONE!!'

In any case, one way to determine whether it's the Streamyx infrastructure or something on the US side is to attempt to connect using an alternative method like dial-up (TMnet or Jaring). If you can get acceptable latency, then it's most likely Streamyx messing up.

There we go... AT&T (or whatever US gateway Malaysia is on) is absolved.

My conclusion... there was very little, if any, issue with the US gateway Malaysia uses, as shown my the lack of problems users of dial-up and other services have encountered.

TMnet did do a spot of maintenance, I imagine, which is why Streamyx users outside Klang Valley have seen things go back to normal lately.

Where to now? I expect they'll have to sort out the node congestion in the Klang Valley, as well as work out some issues with the routing tables.

Be optimistic, go have a cup of teh tarik instead of venting your frustrations here, and hopefully things will get back to normal (or whatever normal translates to on Streamyx) by the end of the day.

For those who are going through cold turkey, a chapalang dial-up modem is only RM20 or so at Lowyat. Getting one ought to tide you for the time being.

Hmmm, this thread got all quiet since lunchtime.

Have you all finally managed to get back on to play, or has Streamyx died completely that you can come on to post?

No, it doesn't... but I think some of us are still paying for 20-odd ringgit TMnet subscription which we were using before Streamyx came along. At least I am because I wanted to keep my @tm.net.my email address.

I no longer have a dial-up modem tho... Anyone want to lend me one? I'm in the Damansara area

Well, tell him to fix Damansara/TTDI first then

Got disconnected at about 1:40am last night for no reason, and then couldn't reconnect.

Anyone else got it as well?

Quite annoying because I was 10 minutes from finishing Dire Maul North.

For what it's worth, all servers are going to be down between 7pm and 10pm our time tonight.

Hope they get it sorted out by the time they come back up. I'm looking at a late night session again.

Well, I guess Xeo will have to talk with his Streamyx supervisor 'friend' again, or at least someone else can follow up.

That said, the supervisor 'friend' apparently did say that the problem will be fixed for everyone 'early next week'.

Than again, at this point in time, I have as much trust in the word of a Telekom official than I have in a Malaysian becoming F1 world champion

The fact that we were having sub-500 latencies means only one thing to me...

Streamyx punya routing table kena baham murloc

or

routing table Streamyx dibaham murloc

depending on which you prefer to describe the situation

Some of us cannot seem to hit the 218.* and 60.* IPs, it seems.

But then, I give up after 5 mins or so... no patience!

Can anyone write a VB script to automatically connect and disconnect until you get either the 218.* or 60.* IP range.


This post has been edited by wildside: Apr 2 2005, 10:37 AM

If 219.* is indeed being blocked by AT&T, then I'm pretty sure it's for a good reason - cracking attempts, DOS attacks or something like that.

In which case, good job, Streamyx community of Malaysia! You have probably shown that you lack the maturity to use broadband connections without engaging in illegal activities.

I suppose I could get a few friends Stateside to check up on this for me.

Consider the fact that even if you were not blocked by the DESTINATION IP - Blizzard WoW server, in this case - you are still being blocked by some of the nodes along the way, forcing your connection to take a much longer way to the destination.. resulting in higher pings.

Here's how abuses are handled most of the time...

When an abuse is detected, the target ISP contacts the ISP of the offender to request for action. Offender's ISP in most countries like the US, Canada and Australia almost always take action, resulting in the offender being banned, at which point life carries on.

Blanket IP range bans only occur when the target ISP does not get the cooperation of the offender's ISP, giving it no choice but to block entire IP ranges. I believe this is what has happened here, if Streamyx 219.* is indeed being blocked.

AT&T
Streamyx, we have detected an abuse event coming from 219.95.*.* at 09:56 on the 11th of March 2005. We request that you take action.

Streamyx
Sorry, we don't know.. Can't help you.

AT&T
We have no choice but to block the entire IP range then *click*


So, you have two culprits here...

1) The original offender(s)
2) The ISP for not cooperating, either through incompetence or idiocy.

Can't really do anything about the ISP, so for eff-ing sakes, guys... you can do something about the other one. Stop doing anything that gives them the slightest reason to block the IPs, eh?

But like I said earlier, I'll just get a friend on the other side to check up on this, although I'm not personally affected by this mess to any great extent.



This post has been edited by wildside: Apr 4 2005, 10:47 AM

In any case, can someone on 219.95.*.* log into an eastern and western server at about 11:40 and report the latency rates you are getting in-game?

For those that don't recall the server locations before Blizz amalmagated them...

You can use Tichondrius for west, and maybe Stormrage for east.