andrienne.. can do me a favour.. u try open www.tagged.com see can browse easily or not.. and another thing is www.youtube.com how the speed from those site..

but urs is 115.132.*.* and mine / aziz 115.133.*.*

This post has been edited by zfitri: May 24 2009, 03:30 PM

Tmn Pasir Putih bro..
My brother and my friend also pening with this matter.

---

Added on May 24, 2009, 3:55 pmi try to surf to tagged.com.
its very slow..

my brother at Tmn Scientex, and my friend at Tmn Mawar

This post has been edited by aziz79: May 24 2009, 03:56 PM

as long as we within the 115.133.*.* ip range we will face this problem..

really??? I 60.48-60.54 range also slow...

What is the problem: streamyx so leg. cannot download anything
IP Range: 60.50.43.**
Area: Sungai Nibong
State: Penang
When this problem started: allmose 1 month
dont know what to do...

possible... or maybe got any problem with they stuff

What is the problem: streamyx so leg. cannot download anything
IP Range: 60.50.43.**
Area: Sungai Nibong
State: Penang
When this problem started: allmose 1 month
dont know what to do...

which part of pasir gudang u live?
have u make report to streamyx?

no use laa.. report 100? hahaha the same answer they gave.. donno what to do now..

hi there,

sorry for the late reply. can browse the tagged.com with ease and streaming from youtube is quite fast as per normal 1mb speed.

my internet is stil the same as per the past few days

ping google, streamyx all ok <50 <20 ms

speed test ping OK, but stuck at "preparing download" - cannot even connect to ANY server including KL, penang, sg to do speedtest.

i couldn't even load speedtest site yesterday night. thank god it's abit better today...if not, i will be calling them up to scold again even tho the customer service ppl can't do anything, i still can't surpress my 'anger'

my speedtest just now:



normally dl can reach about 0.65 mbps and upload about 0.35mpbs. today still abit slow for dl. but browsing still acceptable at an ease.

Reply from 202.188.1.5: bytes=32 time=363ms TTL=57
Reply from 202.188.1.5: bytes=32 time=327ms TTL=57
Reply from 202.188.1.5: bytes=32 time=335ms TTL=57
Reply from 202.188.1.5: bytes=32 time=329ms TTL=57
Reply from 202.188.1.5: bytes=32 time=346ms TTL=57
Reply from 202.188.1.5: bytes=32 time=368ms TTL=57
Reply from 202.188.1.5: bytes=32 time=330ms TTL=57
Reply from 202.188.1.5: bytes=32 time=331ms TTL=57
Reply from 202.188.1.5: bytes=32 time=325ms TTL=57
Reply from 202.188.1.5: bytes=32 time=332ms TTL=57
Reply from 202.188.1.5: bytes=32 time=316ms TTL=57
Reply from 202.188.1.5: bytes=32 time=319ms TTL=57
Reply from 202.188.1.5: bytes=32 time=314ms TTL=57
Reply from 202.188.1.5: bytes=32 time=329ms TTL=57
Reply from 202.188.1.5: bytes=32 time=334ms TTL=57
Reply from 202.188.1.5: bytes=32 time=331ms TTL=57

Ping statistics for 202.188.1.5:
Packets: Sent = 3342, Received = 3338, Lost = 4 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 746ms, Average = 298ms

Pinging 202.188.1.5 with 32 bytes of data:

Reply from 202.188.1.5: bytes=32 time=44ms TTL=53
Reply from 202.188.1.5: bytes=32 time=44ms TTL=53
Reply from 202.188.1.5: bytes=32 time=44ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53
Reply from 202.188.1.5: bytes=32 time=44ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53
Reply from 202.188.1.5: bytes=32 time=44ms TTL=53
Reply from 202.188.1.5: bytes=32 time=43ms TTL=53

Ping statistics for 202.188.1.5:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms

---

Added on May 24, 2009, 8:56 pmPinging www-real.wa1.b.yahoo.com [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=242ms TTL=52
Reply from 209.131.36.158: bytes=32 time=244ms TTL=50
Reply from 209.131.36.158: bytes=32 time=242ms TTL=52
Reply from 209.131.36.158: bytes=32 time=243ms TTL=52
Reply from 209.131.36.158: bytes=32 time=242ms TTL=50
Reply from 209.131.36.158: bytes=32 time=242ms TTL=52

Ping statistics for 209.131.36.158:
Packets: Sent = 6, Received = 6, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 242ms, Maximum = 244ms, Average = 242ms

This post has been edited by DeanKueh: May 24 2009, 08:56 PM

hi, can some1 shed some light wat does this mean actually?

Reply from 202.188.1.5: bytes=32 time=44ms TTL=53

the 202.188.1.5 is the server u are pinging?
what is the 'acceptable' value for the time?
and wat is TTL
and in wat condition we can determine our line is stable?

202.188.1.5 is TM's second DNS server.

Acceptable value would be <50ms

TTL means Time To Live

Your line is stable if your Downstream and Upstream SNR Margin is >20dB and Line Attenuation <20.

This post has been edited by Irzani: May 24 2009, 11:00 PM

Based on the test result looks ok (i'm using 512k), but in real life, browsing is slow....

It seems like TMline is back into action.

so it's confirmed that this problem is widespread and almost everyone is facing it?

either
-browing ok, dl not ok
-browsing not ok, dl ok (rare)
- all not ok

technician should be coming tomorrow (I hope) so what should i tell him to check? the port / dslam stuff? there was once they went to this "exchange" and replaced some wire or something inside.. not sure.