Tuesday, March 06, 2007
SERVICE INTERRUPTION


TM Berhad wishes to inform our tmnet streamyx customers that it will be performing a service maintenance exercise on its Streamyx system from 5 March 2007 till 16 March 2007 in various areas nationwide.



The date of the exercise and its affected areas are detailed below:



Attached thumbnail(s)

... my record can up to 20days without disconnect.



This post has been edited by yangxi: Apr 14 2007, 11:16 PM


Attached thumbnail(s)

damm..
MELAKA here ,browse speed very slow! starting this week~.

google delay 2sec to open.

---

Added on April 16, 2007, 1:43 amTMNUT change CEO ?

this guy already kick out ?






This post has been edited by yangxi: Apr 17 2007, 01:25 PM

damm nut ,google ping 2297ms !!

Pinging www.l.google.com [64.233.189.104] with 32 bytes of data:

Reply from 64.233.189.104: bytes=32 time=2297ms TTL=245
Reply from 64.233.189.104: bytes=32 time=2276ms TTL=245
Reply from 64.233.189.104: bytes=32 time=2296ms TTL=245
Reply from 64.233.189.104: bytes=32 time=2270ms TTL=245

Ping statistics for 64.233.189.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2270ms, Maximum = 2297ms, Average = 2284ms

damm,
Always timeout when loading page during night time.
Local site Cari,Lowyat bbs also cause same problem.

---

Added on April 30, 2007, 1:18 amroute problem ?

This post has been edited by yangxi: Apr 30 2007, 01:19 AM


Attached thumbnail(s)

again.$%$# Melaka here very slow , no speed for BT

Pinging www.l.google.com [64.233.189.104] with 32 bytes of data:

Reply from 64.233.189.104: bytes=32 time=1653ms TTL=245
Reply from 64.233.189.104: bytes=32 time=1649ms TTL=245
Reply from 64.233.189.104: bytes=32 time=1655ms TTL=245
Reply from 64.233.189.104: bytes=32 time=1631ms TTL=245

Ping statistics for 64.233.189.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1631ms, Maximum = 1655ms, Average = 1647ms

This post has been edited by yangxi: May 31 2007, 11:50 PM

today totally can't access most china,taiwan website.

Pinging zol.com.cn [211.154.205.43] with 32 bytes of data:

Request timed out.
Reply from 211.154.205.43: bytes=32 time=2129ms TTL=235
Reply from 211.154.205.43: bytes=32 time=2122ms TTL=235
Reply from 211.154.205.43: bytes=32 time=2110ms TTL=235

Ping statistics for 211.154.205.43:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 2110ms, Maximum = 2129ms, Average = 2120ms

http://www.tm.net.my/tmnet2006/contents/co...&type=News&pg=1

Latest News
Saturday, June 30, 2007
ANNOUNCEMENT

We wish to inform our customers that the Internet service is currently experiencing an increased latency/degradation in performance specifically for its international links to United States of America (USA).

As a result, our Internet customers may experience some delay when accessing content and websites hosted outside of Malaysia, especially in US. We are conducting an upgrading exercise of our international bandwidth links, where an additional 10Gbps of capacity through Hong Kong is being implemented.

As the moment, 90% of the upgrading process is completed and we expect the upgrading process to be fully completed by 2nd July 2007.

We are pleased to inform you that this exercise is part of TM's upgrading plan for its international links in 2007, which will help reduce traffic congestion and improve customers' Internet experience. There are also plans for further upgrade of our international bandwidth capacity in September 2007.

Telekom Malaysia apologizes for any inconvenience caused, whilst at the same time, we would like to assure you that we are upgrading our services to serve you better.



Thank you

This post has been edited by yangxi: Jun 30 2007, 06:54 PM

today worst !! timeout most china page.

and cannot connect emule server.

yeah.. 60.53.x.x ip better

just ping tw.news.yahoo.com


60.48.x.x = ~520ms
60.51.x.x = ~1000ms
60.53.x.x = ~110ms

IP: 60.53.x.x
MELAKA

c:\ping www.tm.net.my

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

Reply from 202.71.97.48: bytes=32 time=18ms TTL=116
Reply from 202.71.97.48: bytes=32 time=17ms TTL=116
Reply from 202.71.97.48: bytes=32 time=16ms TTL=116
Reply from 202.71.97.48: bytes=32 time=16ms TTL=116

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


c:\ping 202.188.0.133

Pinging 202.188.0.133 with 32 bytes of data:

Reply from 202.188.0.133: bytes=32 time=31ms TTL=248
Reply from 202.188.0.133: bytes=32 time=33ms TTL=248
Reply from 202.188.0.133: bytes=32 time=31ms TTL=248
Reply from 202.188.0.133: bytes=32 time=27ms 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 = 27ms, Maximum = 33ms, Average = 30ms


c:\ping tw.news.yahoo.com

Pinging tw-news-tpc-fo.yahoo-ap1.akadns.net [203.84.203.127] with 32 bytes of data:

Reply from 203.84.203.127: bytes=32 time=74ms TTL=47
Reply from 203.84.203.127: bytes=32 time=74ms TTL=47
Reply from 203.84.203.127: bytes=32 time=75ms TTL=47
Reply from 203.84.203.127: bytes=32 time=74ms TTL=47

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


c:\ping www.yahoo.com

Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=220ms TTL=51
Reply from 209.131.36.158: bytes=32 time=217ms TTL=51
Reply from 209.131.36.158: bytes=32 time=218ms TTL=51
Reply from 209.131.36.158: bytes=32 time=215ms TTL=51

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

This post has been edited by yangxi: Sep 3 2007, 11:51 PM

most site timeout ... lowyat forum also got problem`...

This morning can't browsing any website , until now just can.

60.53 ip slow now days. suggest download using proxy http://www.cybersyndrome.net/

#$^*^ 1-2k/b up down speed for P2P connection.

What happen today??



This post has been edited by yangxi: Dec 1 2007, 04:42 PM

$&%$ Slow down again !!

ping www.yahoo.com

Pinging www.yahoo-ht3.akadns.net [87.248.113.14] with 32 bytes of data:

Reply from 87.248.113.14: bytes=32 time=510ms TTL=41
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 87.248.113.14:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 510ms, Maximum = 510ms, Average = 510ms

yeah , Taiwan HINET PROBLEM!!




Attached thumbnail(s)

Mandatory Standards for Quality of Service
http://forum.lowyat.net/index.php?showtopic=486176&hl=

Everything slow down today .. google keep timeout.!~

@#$^%#

1mbps Streamyx username speed cap back from 2MB (195kb/s) back to 1.5mb (155kb/s)