Last night they have maintenance at Gombak yet I am in Pg was disconnected just like begining of the month where they did some work at another place. So called upgrade was not my area but I am affected by it, each time this thing happens usually took 15mins to get back in.

Their announcement claims "upgrade" happened in 11.00pm, Tuesday, 26th May 2009 until 6.00am, Wednesday, 27th May 2009. So by now there shouldn't be any problems, then again this is TMNut we are talking about, upgrade or fix one place and probably broke several are places doing it

I never had issues with their "upgrades" other than usual slowness, but this month each time they "upgrade" elsewhere I seem to encounter a few disconnection issue, I rarely get disconnected as my line is stable before this as well.

If their technicians are really this bad, they should consider getting outside professional help.

I am wondering if they are running out of bandwidth or poor routing or both

Whichever it is, we will continue to suffer. I wonder what excuse they will give out, probably something to do with our fault again. They always shift the blame to us as usual.

Must be new tactic. Earlier of the month, I called them to make an enquiry about availability of 4mb for my area, waited 1 hour or so, dial redial etc and making my ear hurt from waiting... finally I manage to get through I ask my questions, not yet finish asking (say 5-8 sec after tm hotline pickup the call), he hung up on me.

Calling TM isn't good for my blood pressure, was for a moment thinking of throwing my phone into the wall.

Which site you ping? I am at moment using 60.49.xxx.xxx ping google seems ok except for once a while getting timeouts.

C:\>ping www.google.com

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

Reply from 74.125.95.99: bytes=32 time=223ms TTL=48
Reply from 74.125.95.99: bytes=32 time=222ms TTL=48
Reply from 74.125.95.99: bytes=32 time=224ms TTL=47
Request timed out.

Ping statistics for 74.125.95.99:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 222ms, Maximum = 224ms, Average = 223ms


Target Name: www.google.com
IP: 74.125.95.103
Date/Time: 5/29/2009 7:38:52 AM

2 12 ms 11 ms 11 ms [219.93.217.13]
3 11 ms 12 ms 11 ms [58.27.103.190]
4 17 ms 17 ms 17 ms [203.106.128.73]
5 20 ms 20 ms 19 ms [210.187.15.254]
6 20 ms 20 ms 113 ms [210.187.129.131]
7 18 ms 17 ms 17 ms [58.27.105.105]
8 N/A 19 ms 19 ms [203.106.6.186]
9 26 ms 25 ms 25 ms [58.27.106.226]
10 26 ms 26 ms 26 ms [74.125.50.229]
11 27 ms 26 ms 26 ms [209.85.243.156]
12 102 ms 99 ms 102 ms [72.14.232.115]
13 100 ms 101 ms 100 ms [209.85.255.37]
14 184 ms 184 ms 185 ms [216.239.43.212]
15 212 ms 210 ms 210 ms [209.85.241.210]
16 222 ms 221 ms 222 ms [209.85.243.116]
17 N/A N/A 222 ms [209.85.241.37]
18 N/A N/A 222 ms [209.85.240.49]
19 224 ms 224 ms 222 ms iw-in-f103.google.com [74.125.95.103]

Ping statistics for www.google.com
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 222ms, Maximum = 224ms, Average = 223ms

Everything is dead, I couldn't even browse to here

Oh crap...


UPGRADING OF TM CORE NETWORK

Telekom Malaysia Berhad ™ wishes to inform its customers that it is migrating its existing core network to the latest network technology to facilitate the ongoing improvements of our network performance and service quality. The migration will allow TM to provide a more integrated service proposition to support a large ecosystem of applications.

The infrastructure migration will take place in two stages on the following dates and time-periods:

1. Friday, 12 June 2009, 11 pm till Saturday, 13 June 2009, 6 am
2. Friday, 19 June 2009, 11 pm till Saturday, 20 June 2009, 6 am

Therefore, all our Internet and Voice over Internet Protocol (VoIP) such as iTalk and Home Prepaid customers nationwide may experience a disruption of service during the stipulated period. We would like to assure our customers that the services would resume to normal after this period.

219.93.178.162:3128 still works but slowed

I thought according to MCMC its 90% effective of 1 Jan 2009 ? I noticed TM's site is 70% I am a bit confused.

Link: MCMC QoS Broadband

I might be wrong I think 115.13X range is under cache... I kept getting Gateway error while trying to access lowyat forums...


504 Gateway Time-out
nginx/0.6.35


Worse still TM Speedometer is giving all sorts of weird false test results eg 7mb 15mb etc... Only P1 is not affect as first test if too fast it seems to be redirect to bigger file for testing so 2nd test will get correct speed.


Really hard to access lowyat forum right now...

Just tried Speedtest.net



Can say under cache.

This post has been edited by BugFace: Jul 10 2009, 07:56 PM

They are getting smart having us under cache, so if we complain speed, we asked to do speed test at TM's Speedometer which will show higher than normal speed. Which to them means no speed issues.

Gateway error along with all the weird speed test results should mean we are under cache. *sigh*

Usually both I think...

What IP Range? I am stuck in 115.13x. No issues surfing google... but 115.13x is under cache so might be different. Also I don't use TM's DNS Server either...

Tested 115.13(3/4/5).XXX.XXX all 3, the tracert shows 2xx ms.


Ip Range 115.134
Target Name: www.google.com
IP: 74.125.65.106
Date/Time: 7/14/2009 4:51:39 PM

2 9 ms [219.93.219.181]
3 17 ms [10.55.32.120]
4 50 ms [58.27.106.238]
5 49 ms [219.94.9.10]
6 51 ms [209.85.241.58]
7 108 ms [209.85.249.236]
8 182 ms [216.239.43.212]
9 222 ms [209.85.241.210]
10 250 ms [209.85.249.18]
11 259 ms [209.85.242.215]
12 259 ms [72.14.239.131]
13 266 ms [209.85.253.214]
14 257 ms gx-in-f106.google.com [74.125.65.106]

This post has been edited by BugFace: Jul 14 2009, 05:11 PM