damn laggy 218 ip

damn farking slow now

Pinging www.tm.net.my [202.71.97.48] with 32 bytes of data:

Reply from 202.71.97.48: bytes=32 time=388ms TTL=118
Reply from 202.71.97.48: bytes=32 time=462ms TTL=118
Reply from 202.71.97.48: bytes=32 time=395ms TTL=118
Reply from 202.71.97.48: bytes=32 time=333ms TTL=118

Ping statistics for 202.71.97.48:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 333ms, Maximum = 462ms, Average = 394ms

Intl site is much higher! Its been happening too frequently!!! tmnet boleh!

guys what ur ping to www.tm.net.my now? online fps gaming is impossible. crap this is too frequent these days.

This post has been edited by skippro: Apr 22 2007, 07:55 PM

i cannot login to msn

wow pings shot up again at certain hours of the day, wtf tmnet doing xhibai

yep got disconected about 1am something just able to connect back. f&&K TMNUT

tmnut - pure incompetency! Its obvious now, tmnet blaming bittorrent users for network congestion to a halt was exaggerated; just another excuse to cover up their faults.

---

Added on July 26, 2007, 10:11 pmtmnut - pure incompetency! Its obvious now, tmnet blaming bittorrent users for network congestion to a halt was exaggerated; just another excuse to cover up their faults.

This post has been edited by skippro: Jul 26 2007, 10:11 PM

yep some sites cannot surf. i even have problem with google

crap i think Kuala Pauh exchange something wong alreadi (happy garden kl)


Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=9641ms TTL=249
Reply from 202.188.0.133: bytes=32 time=9591ms TTL=249
Reply from 202.188.0.133: bytes=32 time=9607ms TTL=249
Reply from 202.188.0.133: bytes=32 time=9593ms TTL=249

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

This post has been edited by skippro: Sep 4 2007, 12:01 AM

hehe i added 9 in front of the numbers for added effect mah...damn pissed @ tmnutz now.....hmmm yesterday and today, connection resume normality at exactly 12:00am but after few hours slow back. basted tmnut die die die

This post has been edited by skippro: Sep 4 2007, 12:21 AM

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=518ms TTL=249
Reply from 202.188.0.133: bytes=32 time=514ms TTL=249
Reply from 202.188.0.133: bytes=32 time=514ms TTL=249
Reply from 202.188.0.133: bytes=32 time=420ms TTL=249

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



i complained earlier last week about high latency to local servers. been ok for this few days and today problem again!!

hi guys whats your ping times to 202.188.0.133 right now? mine still high, surfing damn laggy.

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=485ms TTL=248
Reply from 202.188.0.133: bytes=32 time=464ms TTL=248
Reply from 202.188.0.133: bytes=32 time=514ms TTL=248
Reply from 202.188.0.133: bytes=32 time=483ms 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 = 464ms, Maximum = 514ms, Average = 486ms


WTF TMNUT

somebody pls show me ur pings to 202.188.0.133 now......thanks

thanks guys. this means tmnut didnt fix the problem in my area earlier........grrrr besok i have to make report again sighh....

my ping to local servers been goiing up and down past few weeks, i've so far made 3 reports. When problem appears gone, tmnut calls up to confirm. after a day or two ,problem back. Like this, susah lah

This post has been edited by skippro: Sep 17 2007, 11:42 PM

Can u guys ping 202.188.0.133 and/or other www.tm.net.my for me please. I'm getting abnormal ping everyday at certain hours, already made 4 reports & no improve. Just need to know whether its only my area problem. Thank u.

This post has been edited by skippro: Sep 20 2007, 09:04 PM

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=322ms TTL=248
Reply from 202.188.0.133: bytes=32 time=273ms TTL=248
Reply from 202.188.0.133: bytes=32 time=300ms TTL=248
Reply from 202.188.0.133: bytes=32 time=304ms 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 = 273ms, Maximum = 322ms, Average = 299ms

60 or 218 all same. f&^k u tmnut

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=1078ms TTL=248
Reply from 202.188.0.133: bytes=32 time=1066ms TTL=248
Reply from 202.188.0.133: bytes=32 time=1088ms TTL=248
Reply from 202.188.0.133: bytes=32 time=1042ms 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 = 1042ms, Maximum = 1088ms, Average = 1068ms

inging www.jaring.my [61.6.32.105] with 32 bytes of data:



Reply from 61.6.32.105: bytes=32 time=1109ms TTL=246
Request timed out.
Reply from 61.6.32.105: bytes=32 time=1020ms TTL=246
Reply from 61.6.32.105: bytes=32 time=1023ms TTL=246

Ping statistics for 61.6.32.105:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1020ms, Maximum = 1109ms, Average = 1050ms



This post has been edited by skippro: Sep 21 2007, 01:31 AM