YES, STREAMYX IS GETTING FROM BAD TO WORSE


IN THE BEGINNING I GET AROUND 170kbs for 1 m.......now it's slower by at least 30% to around 110kbs.

What you need to do is to immediately go to Streamyx Speedometer (google it) , test your speed, take 3 screen shots @ 3 different intervals then upload it together with your complain to CFM http://complaint.cfm.org.my
TM will call u within 3 days and takes about 7 days to fix your problem at most
if it happens to you again, DONT CALL 100 (because they ll just reset your port)
just open another file

And they want to do HSBB........


Other nation got 10MBps long time ago..........

4 MB in Bangsar no problem after 12 am.

my streamyx (1mbs) download speed during day time 8am-1am less than 40kb/s sometimes can even reach 500bytes per sec ><

but the speed will return to normal 150-200kbs around 2am in the moring

what cause the slow speed in the day time??

anyone suffering the same problem?

Same here in Mines area..
Guess shitmix is throtling all dl speed from RS, MU, MS, NL, etc..
Shit!!

Check this out!



Finally my upload speed is higher than my download speed!

Shame on you screamyx!

I want to make a complain to TMNET Integrated Complaint Management System.. https://tmbill.tm.net.my/iCoMSWeb/

Guess what? The site is down..

I guess there are too many complaints right now..they probably saying "Shut the F8ck up customers. Use that snailspeed connection and live with it".

i also get a low speed here, shame on you screamyx! !!!

I just realised my upload speed being capped to 256kbps.. from 384kbps (suppose to be that speed right? for 1mbps package).

see this screenshot as proof.. can I lodge a complain?


edit: I used to get 384kbps connection but it changed since last week..

This post has been edited by Sky.Live: Apr 4 2010, 02:22 AM

I had it with P1 Wimax, how do i able to cancel it? or should i complain until they able to help me cancel without paying penalty?

Hey folks, I'm having the same problem here for the past 3 days here in Ipoh, Jelapang Area, Taman Rishah.
Spoke with TM line man and he said that the reason why it's uber slow in my area is because they are installing new fiber optic cables and adding more ports.
Said it'll be back to normal after 2 months.

woot-woot..
after 2 months..

if all user got that fiber optic..
i don't care..
or maybe some nice constant speed after that..

2 hours, disconnected about 7/8 times...
my line already fixed and stable since a year ago..
but now after unifi launch, randomly dc >___>
is it coincidence..?

now I got a new ip range, 175.144.*.*
well.. it's new for me..... usually i got 115...
..
...
....
dc again just now.... and back to 115 @___@

This post has been edited by andy0212: Apr 9 2010, 09:56 PM

C:\Users\Dean>ping 202.188.0.133 -t

Pinging 202.188.0.133 with 32 bytes of data:
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=136ms TTL=245
Reply from 202.188.0.133: bytes=32 time=49ms TTL=246
Reply from 202.188.0.133: bytes=32 time=91ms TTL=245
Reply from 202.188.0.133: bytes=32 time=40ms TTL=246
Reply from 202.188.0.133: bytes=32 time=56ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=63ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=46ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=61ms TTL=246
Reply from 202.188.0.133: bytes=32 time=43ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=46ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=66ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=43ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=67ms TTL=245
Reply from 202.188.0.133: bytes=32 time=42ms TTL=246
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=37ms TTL=245
Reply from 202.188.0.133: bytes=32 time=42ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=42ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=37ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=37ms TTL=245
Reply from 202.188.0.133: bytes=32 time=50ms TTL=246
Reply from 202.188.0.133: bytes=32 time=63ms TTL=246
Reply from 202.188.0.133: bytes=32 time=43ms TTL=245
Reply from 202.188.0.133: bytes=32 time=49ms TTL=246
Reply from 202.188.0.133: bytes=32 time=42ms TTL=245
Reply from 202.188.0.133: bytes=32 time=40ms TTL=245
Reply from 202.188.0.133: bytes=32 time=45ms TTL=246
Reply from 202.188.0.133: bytes=32 time=185ms TTL=245
Reply from 202.188.0.133: bytes=32 time=45ms TTL=246
Reply from 202.188.0.133: bytes=32 time=45ms TTL=246
Reply from 202.188.0.133: bytes=32 time=67ms TTL=245
Reply from 202.188.0.133: bytes=32 time=43ms TTL=246
Reply from 202.188.0.133: bytes=32 time=37ms TTL=245
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=37ms TTL=245
Reply from 202.188.0.133: bytes=32 time=41ms TTL=246
Reply from 202.188.0.133: bytes=32 time=42ms TTL=246
Reply from 202.188.0.133: bytes=32 time=36ms TTL=245
Reply from 202.188.0.133: bytes=32 time=49ms TTL=246
Reply from 202.188.0.133: bytes=32 time=43ms TTL=245
Reply from 202.188.0.133: bytes=32 time=43ms TTL=245

Ping statistics for 202.188.0.133:
Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 185ms, Average = 48ms

KK SABAH

anyone experiencing weird pings?

I've been wondering about this too. And always on weekends these days, I can't successfully download files from RS servers. Line would just break connection to the internet all of a sudden, which also breaks off the download. Then a seconds later, it resumes like there was nothing wrong. My wireless didn't even disconnect the entire time. It's connected, only not to the internet. If I can give Streamyx the finger and simply potong, I really would. But too bad, I can't.

lag spikes and lost packets to international websites. Can't play HoN without lag.

FML.

Start of this month i have been getting horrible latency on international sites. At first i thought its a random thing, being Streamyx and all,

Then i notice while i was playing my WoW, lag spikes would start at around 10am, websites not loading properly, Youtube wont load, my WoW registered a 5k ms latency. This goes on until in the morning around 3am. Then all of the sudden everything went smooth. My DDL goes up, my Youtube loads flawlessly.

This happens everyday like clockwork. WTF!

IP Range 115.(133-135).x.x

i think this same goes to me as well. my ip range same as you. but i'm from selangor, mine started slowed down around 3p.m onwards till late. by the way. my current package is 1mb, i get this 115 ip range due to my upgrade to 4mbps had failed. is it this ip range slow for 1mbps? oh my god, damm hectic

after i read your post it happened to me F*()@!&#*(&!@#