mine is with modem package and the modem is down for more than 1 week, i am now using dial-up sic! bloody tmnut never bother to replace my modem, i want to claim rebate, please where can i report?

Just like my connection here in Genting Highlands, our copper phone lines are connected to a RDSLAM means your copper run to nearest fiber SDH/PDH is only around 200 ~ 300 meters.

The signal is excellent when one is connected to a remote RDSLAM rather than having your copper to go all the way to a DSLAM

Last time i had same problem, complain to the nuts and they changed
to new port only then the ping stable

looks like the problem is not with the isp, looks like localised problem with your system traffic or with dslam or rdslam and do not run ping test during torrent session cos for sure get high timeouts... anyway this is my results without torrent session.

something is seriously gone wrong with the nuts

suddenly i am on 124.82.xx.xx ip !!



Pinging 202.188.0.133 with 32 bytes of data:
Reply from 202.188.0.133: bytes=32 time=226ms TTL=248
Reply from 202.188.0.133: bytes=32 time=221ms TTL=248
Reply from 202.188.0.133: bytes=32 time=222ms TTL=248
Reply from 202.188.0.133: bytes=32 time=227ms TTL=248
Reply from 202.188.0.133: bytes=32 time=226ms TTL=248
Reply from 202.188.0.133: bytes=32 time=223ms TTL=248
Reply from 202.188.0.133: bytes=32 time=232ms TTL=248
Reply from 202.188.0.133: bytes=32 time=227ms TTL=248
Reply from 202.188.0.133: bytes=32 time=230ms TTL=248
Reply from 202.188.0.133: bytes=32 time=231ms TTL=248
Reply from 202.188.0.133: bytes=32 time=234ms TTL=248
Reply from 202.188.0.133: bytes=32 time=233ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=235ms TTL=248
Reply from 202.188.0.133: bytes=32 time=231ms TTL=248
Reply from 202.188.0.133: bytes=32 time=229ms TTL=248
Reply from 202.188.0.133: bytes=32 time=227ms TTL=248

Ping statistics for 202.188.0.133:
Packets: Sent = 17, Received = 16, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 221ms, Maximum = 235ms, Average = 228ms

do you think that my port is having a problem or it's with the nuts?

i am having terrible ping timeout to lowyat.net
does anyone else having this problem or is it just my connections??

lowyat.net ping latency 23ms
but still have intermittent packet loss

wtf!! still sucks

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=23ms TTL=248
Reply from 202.188.0.133: bytes=32 time=26ms TTL=248
Reply from 202.188.0.133: bytes=32 time=45ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=21ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=21ms TTL=248
Reply from 202.188.0.133: bytes=32 time=21ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=21ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=25ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=22ms TTL=248
Reply from 202.188.0.133: bytes=32 time=19ms TTL=248
Reply from 202.188.0.133: bytes=32 time=19ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=19ms TTL=248
Reply from 202.188.0.133: bytes=32 time=19ms TTL=248
Reply from 202.188.0.133: bytes=32 time=19ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Reply from 202.188.0.133: bytes=32 time=20ms TTL=248
Request timed out.

Request timed out.
Reply from 202.188.0.133: bytes=32 time=38ms TTL=248
Reply from 202.188.0.133: bytes=32 time=31ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=41ms TTL=248
Reply from 202.188.0.133: bytes=32 time=38ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=42ms TTL=248
Reply from 202.188.0.133: bytes=32 time=46ms TTL=248
Reply from 202.188.0.133: bytes=32 time=47ms TTL=248
Reply from 202.188.0.133: bytes=32 time=47ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=42ms TTL=248
Request timed out.
Reply from 202.188.0.133: bytes=32 time=56ms TTL=248
Reply from 202.188.0.133: bytes=32 time=59ms TTL=248
Reply from 202.188.0.133: bytes=32 time=55ms TTL=248

STILL SUCKS BIG TIME!!!

what about Maxis Broadband? someone in another forum tried to convince me to use it on HSDPA high speed network. he lives in ss2 and can get 1.4Mbps download
and 800k upload, free wireless modem from maxis, monthly just pay RM68, i am not into gaming just BT 24/7 is this reliable?


>depand pada kawasan la. kawasan saya dpt antara 800k sampai 1.4M sebab >dalam lingkungan High3G (HSDPA). 3GB max cap tu memang ada pada syarat >tapi belum berkuat kuasa lagi. Mungkin tak sebab aku dah dl dekat 30GB (dl >torent/movie) lagi tapi bil bulan bulan still RM 68.00.
>
>oK ni link test guna speed test
>http://img142.imagevenue.com/img.php? mage=11351_21.4.2007_122_590lo.JPG

international p2p throttled
local p2p throttled
now surfing also like sh**, no fu** i am changing my package to 512k

i am using back public proxy server for international sites, at least the whole page are loading in full. FUC** TMNET

soha* now worst than fuc*ing dial-up

i am on 60.48.xx.xxx ip range still shitty as usual:

Pinging 202.188.0.133 with 32 bytes of data:
Reply from 202.188.0.133: bytes=32 time=568ms TTL=248
Reply from 202.188.0.133: bytes=32 time=573ms TTL=248
Reply from 202.188.0.133: bytes=32 time=578ms TTL=248
Reply from 202.188.0.133: bytes=32 time=579ms TTL=248

Ping statistics for 202.188.0.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 568ms, Maximum = 579ms, Average = 574ms



Pinging www.lowyat.net [202.190.197.144] with 32 bytes of data:
Reply from 202.190.197.144: bytes=32 time=578ms TTL=55
Reply from 202.190.197.144: bytes=32 time=584ms TTL=55
Reply from 202.190.197.144: bytes=32 time=580ms TTL=55
Reply from 202.190.197.144: bytes=32 time=574ms TTL=55

Ping statistics for 202.190.197.144:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 574ms, Maximum = 584ms, Average = 579ms

yeah .. post all the NUTS email address here ... that would be very useful

CRC errrors = cummulative errors between the modem and DSLAM/RDSLAM

Good news to ALL, you can now Bypass throttle, just download utorrent 1.8 beta

This post has been edited by shahjees: Feb 10 2008, 08:31 PM