Reporting from JB. On 1mbps package and currently using 60.53 ip range.
Result from trace and ping to google.com at 1 sec interval with 64kb using WinMTR over 200 times.
| ------------------------------------------------------------------------------------------ |
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
| ------------------------------------------------ | ------ | ------ | ------ | ------ | ------ | ------ |
| OSIRIS - 0 | 231 | 231 | 0 | 10 | 151 | 0 |
| 192.168.2.1 - 3 | 231 | 225 | 0 | 137 | 17775 | 17775 |
| No response from host - 100 | 231 | 0 | 0 | 0 | 0 | 0 |
| 219.93.218.21 - 4 | 231 | 224 | 10 | 81 | 511 | 120 |
| 219.94.12.89 - 3 | 230 | 224 | 10 | 72 | 480 | 110 |
| 203.106.4.41 - 3 | 230 | 224 | 10 | 72 | 380 | 160 |
| 203.106.253.225 - 3 | 230 | 224 | 10 | 89 | 360 | 221 |
| 202.188.126.132 - 4 | 230 | 221 | 10 | 100 | 361 | 171 |
| 58.27.103.97 - 4 | 230 | 223 | 20 | 82 | 280 | 150 |
| 10.55.32.73 - 5 | 230 | 219 | 10 | 89 | 470 | 180 |
| 10.55.32.118 - 7 | 230 | 215 | 20 | 85 | 330 | 150 |
| 58.27.106.238 - 32 | 230 | 158 | 40 | 107 | 451 | 161 |
| 219.94.9.10 - 54 | 230 | 107 | 40 | 105 | 251 | 151 |
| 209.85.241.58 - 44 | 230 | 130 | 50 | 110 | 290 | 100 |
| 209.85.249.236 - 52 | 230 | 111 | 110 | 169 | 351 | 110 |
| 209.85.248.131 - 53 | 230 | 110 | 190 | 251 | 551 | 280 |
| 209.85.248.128 - 48 | 230 | 121 | 210 | 278 | 451 | 230 |
| 209.85.249.18 - 44 | 230 | 130 | 220 | 297 | 461 | 291 |
| 209.85.242.215 - 44 | 230 | 129 | 230 | 326 | 591 | 330 |
| 72.14.232.213 - 49 | 230 | 118 | 260 | 473 | 17034 | 17034 |
| 209.85.253.141 - 46 | 230 | 125 | 270 | 343 | 561 | 360 |
| yx-in-f100.google.com - 49 | 230 | 119 | 240 | 336 | 490 | 340 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
The result shows the bottleneck starts at 10.55.32.73 and more significantly at 58.27.106.238 (TM's IP) and worsen at 219.94.9.10 (still is TM's IP).
It appears to me that Streamyx's main problem is that they are repeatedly shoving watermelons thru a garden-hose. Sometimes part of the watermelon gets through, sometimes it stuck.
Lousy equipments may be one cause. Oversold bandwidth could be another cause. And that could be the reason why you may get high-speed but you pages still load slowly as the lost packets had to be repeatedly resend over and over again till they get through. For protocol like TCP that's still fine because you will still get all the data eventually as long as they do not time out for too long, but if you are using UDP or other protocols that do not (or have limited) acknowledge or automatically request the losses, you are in deep shit like me even though your data may not be bandwidth intensive (MMORPGs etc) due to the lack of a minimal sustainable throughput.
There is no point blaming P2P users or others for being bandwidth hogs. The real problem is that TM's infrasture are incapable of handling what they are selling and instead of improving on the infrastruture to ensure a minimal sustainable stability, they roll out ever high speed packages (think bigger watermelons) and continue trying to push them through the same tiny waterhose. The result? Profit increases while quality of service deteriorate severly at a rapid pace.
I remembered about 5 years ago when I was using streamyx on 1mbps and it was smooth as a baby's bottom for months. No drop connections and not much problem. Now it seems like we did be lucky to get a week of smooth connection every month.
As I am a foreigner and it would not be wise for me to get involve in a state-owned monopoly like TM, is there anyone here with contacts with any officials at MCMC and can highlight this to them? The poor quality of broadband services in Malaysia is severly stunning its growth and potential.
Thank you.
This post has been edited by chew13: Jun 25 2009, 10:39 AM