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.

seems like they've switched to alternet as the new route to that part of USA.

This is from Shah Alam near the stadium/Gaint with IP 218.***

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

1 * * * Request timed out.
2 22 ms 25 ms 23 ms 219.93.218.177
3 20 ms 19 ms 21 ms 219.93.216.21
4 21 ms 21 ms 21 ms 202.188.126.132
5 22 ms 22 ms 21 ms 202.188.126.141
6 23 ms 22 ms 21 ms 210.187.15.253
7 22 ms 21 ms 21 ms 210.187.142.1
8 22 ms 23 ms 23 ms vlan150-brf-sw04.tm.net.my [219.93.175.115]
9 22 ms 21 ms 21 ms 210.187.129.171
10 * 1101 ms 1096 ms POS2-2.IG3.SAC1.ALTER.NET [157.130.210.145]
11 * * 1121 ms 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]
12 1120 ms 1118 ms 1120 ms POS7-0.BR5.SAC1.ALTER.NET [152.63.52.229]
13 1116 ms * 1118 ms 204.255.174.174
14 1126 ms 1114 ms 1116 ms tbr1-p013302.sffca.ip.att.net [12.122.11.217]
15 1116 ms 1118 ms 1110 ms gbr5-p100.sffca.ip.att.net [12.122.11.74]
16 1114 ms * 1109 ms gar3-p360.sffca.ip.att.net [12.123.13.157]
17 1126 ms 1122 ms 1128 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
18 1110 ms 1108 ms 1108 ms mdf1-bi8k-1-eth-2-1.lax1.attens.net [12.129.192.
250]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * with the rest request timed out.

From section 28 Shah Alam with 219.95.x.x. Latency seems okay, but with lots of time outs. Connection still pretty unstable.

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

1 * * * Request timed out.
2 21 ms 25 ms 24 ms 219.93.218.177
3 21 ms 19 ms 19 ms 219.93.216.101
4 19 ms 18 ms 19 ms 219.93.155.29
5 20 ms 20 ms 19 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
6 19 ms 21 ms 65 ms 210.187.142.1
7 20 ms 20 ms 20 ms vlan150-brf-sw04.tm.net.my [219.93.175.115]
8 20 ms 20 ms 20 ms 210.187.129.171
9 587 ms 589 ms 588 ms POS2-2.IG3.SAC1.ALTER.NET [157.130.210.145]
10 580 ms * 584 ms 0.so-0-1-0.XR2.SAC1.ALTER.NET [152.63.54.126]
11 581 ms * * POS7-0.BR5.SAC1.ALTER.NET [152.63.52.229]
12 * 538 ms * 204.255.174.178
13 * 542 ms 547 ms tbr1-p013902.sffca.ip.att.net [12.123.13.66]
14 * 536 ms 529 ms gbr6-p100.sffca.ip.att.net [12.122.11.78]
15 534 ms 529 ms 532 ms gar3-p370.sffca.ip.att.net [12.123.13.161]
16 540 ms 547 ms 546 ms mdf1-gsr12-2-pos-7-0.lax1.attens.net [12.122.255
.254]
17 542 ms 550 ms * mdf1-bi8k-2-eth-1-3.lax1.attens.net [12.129.192.
110]
18 * * * Request timed out.
19 * * * Request timed out.

Please people. they said they will fix it on the 20th, but also that they will fix the other cut line by tonight. I suppose they will then route traffic over to that line. It may well end up as 219 having good ping while 218 and 60 get horrid ping times, as this original cut line (not the one cut 2 days ago) seems to be the reason some of you have been facing bad lag for the past 3 weeks. Comprehendo?

Do read the entire article. Don't just go posting that the ship will repair it by the 20th without taking note of other things.

Wasn't it supposed to have been fixed this morning? O_o
0100UTC is supposed to be 8-9am today isn't it ?

Office pc can play.. but it takes me like 25 minutes to get out of IF... stupid old pc!!!!....

(if not mistaken, alternet/uunet is going through apcn2 also... i *think*)

It's probably been fixed but there's some routing issues on the ISP side that needs to be fixed as well probably... static diversion of traffic and all that.. but since it's the weeeeekeeeeendd......

This post has been edited by tarpaucase: Apr 9 2005, 04:32 PM

You get to play WoW at work? Lucky bstrd.

I know I'd get away with it but I have no control over our firewall whatsoever...eh.

I sure hope so. Since they totally change the routing for the 219.95.***.*** since the ACPN2 cable was damaged. At least, TMNet will kind of acknowledge the problem earlier instead of saying there are no problems at all. Also since 219 IP is the most common IP used in the country, your assumption that they will reroute traffic for the better over the 218 IP and 60 IP seems downright obvious.

Fixing the original and internal TMNet problem by tonight, after 3-4 weeks of constant complaints is inexcusable. Remember they went marry-go-round on AT&T fault, then said it's something else, and in the end said that there's no problem whatsoever.

Bottom line, this is standard bull 101. They know they've got problems but won't announce it. Either they're too reckless to find it or just plain lazy. Both are equally unacceptable.

So, it takes an Asia-wide fault to get their house in order. Contrary to popular belief, gamers and P2P'ers make a small percentage of subscribers. It's when the 'normal' web-surfers, mothers, children and business users speak up that TMnet listens. The latest outage sparked it off.

TMNet need public consultation and/or independant testers from experts in each online industry. All respectable ISPs have this utility and it costs next to nothing.

well i sent an email complaining their services now waiting for their reply

just wait .. ill bet thay wont reply or just giive u an auto reply.... tmnut technician ia a piece of joke... they actually a good actor though, they can memorize bunch of script and use it to their costomer.... damm .. is the line ok ready????

They won't bother reading it because the ones who attends to the e-mail doesn't even know what a packet is!

Once I called them, and said I'm having good ping but heavy packet loss. I also tested using their wank modem, but didn't mention it to see how they'll assess the issue.

They then asked me what make my router is, if I have anti-virus, reboot, etc. HAHAHA, they should rename customer support to Computer/Streamyx for Dummies.

heh the script just want to impress non-IT people, so when doing "support" they way look cool, with all teh jargon2 word like they know a shiat/everything ,

imho basically the script for low level technical problem, such as "i want internet", secondary level like "i cant connect to internet", but rite now we asking high level 50~60 question, how can level 20~30 can answer our question

heh they just doing their job, if they know stuff we talking about im sure they not working as streamyx customer support.

/respect to all streamyx support coz they immune/resist to curse/fear/seduce etc etc

HA HA HA HA HA HA HA HA

too.. bad.. is SINGNET :/ ...
anynews from TMNUT yet ?

Nop no news from Tmnuts yet...gosh even my vent ping went up to 21k lol
this is stupid..NERF tmnet!

/dance

AIYOH.. LOL this made me laugh until stomach ache... LOLOLOLOLOLOL...

first sign of WoW withdrawal madness syndrome


You know what would help ? You guys need to get the tmnet network people to get hooked.. AHHH.. THEN they will care... in fact, you no need to complain, they sure fix it ASAP one they need people who really care about their internet connectivity...

Um... I dont think we should shoot down TMNet on the cable disruption issue. After all this is a international cable we're talking here and they, not TMnet, are doing what they can to get it fix. We'll just have to wait it out.

Go ahead an flame them on their customer service, but please don't condemn them for everything.

Do remember this thread is about the bad lags that WoW players have been facing for 3-1/2 weeks already.

Frankly I just hope maintenance team will get the cable fix ASAP. Its not an easy task since the cable distruption is in the sea.

Agreed we shouldn't flame them for the SEA cables. But we should blame them for not giving a single update on the repairs. People had to resort asking third parties like REACH and Singtel for news.

Lostboy, your attitude towards the issue is a perfect explanation why we had the WoW problem in the first place. Malaysia has a backward position because the people themselves willingly "take crap".

I condemn TMNet customer support because they don't measure up to the service that ISPs should provide.
I condemn TMNet's lack of effort in giving the proper IT infrastructure we deserve. My tax money is better spent on charity.

I post my rants on this thread because most people in online gaming understands what real lag is. Whereas, the official streamyx rant thread is catered for everyone.

Interesting... If you read last weeks InTech (I think thursday), it mentioned that Malaysia wanted a share of the gaming industry. YYEEAAAAHHHHH RIIIGGGHHHT... Multiplayer gaming (massively multiplayer or not) is the 'thing' in the gaming industry now. Look at xbox live, Battle.net, etc. With our net infrastructure, there's no way we can support gaming, even at a decent level.

And yeah, WoW still laggy and unstable. Nice~~~~