Problem once again, aih. 'Resolving host' for about 1 minute every page I load. Awesome steamyx.

Just tested...

Damn slow the whole day. Some websites take a while to load, some don't even respond.

Argh, this afternoon the speed damn slow man.. Luckily now i can still bear with it. Can anyone tell me what's exactly the problem??

Cable cut issues

http://blog.mx510.com/2010/06/17/another-c...net-16-07-2010/

Heh, you're one of the lucky ones then, I guess.

You all dam lucky OK!!!
Who can beat me?!!!

My modem gateway, 1st hop already sibeh syiok


This post has been edited by xxerton: Jun 17 2010, 08:54 PM

Is not guess here, I can sense TM Net trying to limit end user speed and this including giving bad pings.


This show the proof.

Looks fine at my side

great great...another shark attack

---

Added on June 17, 2010, 9:36 pmyou can read the future?

This post has been edited by wufei: Jun 17 2010, 09:36 PM

That would be funny answer "shark attack fiber optics...? "

Eh wait, http://www.tm.com.my just remove the announcement about AAG cable... What theee.....

This post has been edited by pengiranijam: Jun 17 2010, 09:41 PM

i had this problem since last Sunday i think....lots of packet loss and extremely high latency for ping to Streamyx dns....

have complained to helpdesk since last mon and until now still not resolved!!!! the issue is sometimes the link is up for awhile and then down again....

really wtf man.....dont know how much longer this will take?

This post has been edited by jutamind: Jun 17 2010, 09:56 PM

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tinklepuff>ping www.tmnet.com.my -t -l 1024

Pinging www.tmnet.com.my [202.71.97.41] with 1024 bytes of data:
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=175ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=163ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=173ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=170ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=173ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=170ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=172ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=165ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=161ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=342ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=1128ms TTL=121
Request timed out.
Reply from 202.71.97.41: bytes=1024 time=190ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=176ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=166ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=174ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=179ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=165ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=157ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=156ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=159ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=164ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=161ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=157ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=182ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=216ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=167ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=247ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=169ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=168ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=165ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=162ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=171ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=167ms TTL=121
Reply from 202.71.97.41: bytes=1024 time=175ms TTL=121

Ping statistics for 202.71.97.41:
Packets: Sent = 61, Received = 60, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 1128ms, Average = 190ms

This is with nothing on not even browser cuz if I load anything it will go haywire.. And I'm in melaka, I usually get response of 40-60ms frm this ping

Hope they fix it quick..

Wow!!! TM planning to attack cable network on 16th July

slow slow slow, damn slow. time to call up 100 and knnccb the customer service.

Ping statistics for 202.188.0.133:
Packets: Sent = 142, Received = 100, Lost = 42 (29% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 1707ms, Average = 142ms

I can't fap RK, NA, BB, PP.

i've been getting the same shit for consecutive nites .... if it's not request timed out then it's destination net unreachable.
i could hardly browse anything at all .....

i just called up 100 and scold the CS and the manager and the damn CEO. ALmost every month is upgrading service for screamyx. Never-ending problem.

shout so much also no use....and the end the problem is still there. i complain from monday until now also useless....problem not resolved.

if my area got p1 wimax coverage, i sure canceled my screamyx line.