They have one lollypop, they need to feed 3 kids. When one kid have the lollypop long enuff, they take if away and give to the other kid, so when the the two other kids complain, they take the lollipop and give it to the complaining kid and give excuse to the other.

tm dont have enuff lollipop.

Until now, still 1k ping with hinet.. *SPEECHLESS*

SIOT!!!!...TMnut taik lembu!!!...

Sigh, i still cant get into most sites.. What is going on with the routing?

Argh! Tak bleh blah~ Slow!

Tracing route to plaync.com [206.127.153.160]
over a maximum of 30 hops:

1 274 ms 178 ms 229 ms 219.93.218.177
2 16 ms 16 ms 15 ms 219.93.216.189
3 145 ms 159 ms 16 ms 210.187.142.1
4 16 ms 15 ms 16 ms 219.93.174.146
5 16 ms 16 ms 17 ms 203.106.6.146
6 247 ms 248 ms 252 ms 219.93.168.234
7 227 ms 227 ms 236 ms ge2-7.fr1.lax.llnw.net [206.223.123.123]
8 227 ms 227 ms 226 ms ve6.fr3.lax.llnw.net [69.28.171.205]
9 246 ms 239 ms 237 ms ge1-2.fr3.phx1.llnw.net [69.28.171.81]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 *

update : problem isnt only in Malaysia. Its throughout Asia and Oceania regon

This post has been edited by onscreen: Apr 24 2007, 09:37 PM

previously 60.53 is fastest for me
and all of sudden in the beginning of this month
that IP range is so so so slow
i'm sticking myself with 124.82 now
don't mention 60.50 IP
it is as slow as 56k

Lucky you for having the ability to get 124.x IP

Mine not that bad, staying at BTHO, everything looks normal to me, just for education purpose, the traceroute bellow shows that the network after ge13-1.br02.sjo01.pccwbtn.net is having problem, local tmnet network looks good, so its not really tmnet fault, eventhough they are screwing up on some area due to bad capacity maintenance.
=====================================
C:\>tracert 206.127.153.160

Tracing route to 206-127-153-160.plaync.com [206.127.153.160]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 16 ms 75 ms 119 ms 219.93.218.177
3 22 ms 10 ms 10 ms 219.93.216.69
4 10 ms 10 ms 10 ms 202.188.126.141
5 10 ms 10 ms 10 ms 202.188.126.132
6 449 ms 578 ms 156 ms 58.27.124.34
7 11 ms 10 ms 10 ms 219.93.173.37
8 210 ms 210 ms 210 ms 219.93.153.150
9 348 ms 349 ms 350 ms ge13-1.br02.sjo01.pccwbtn.net [206.223.116.48]
10 * * * Request timed out.
11 * *
C:\>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 92 ms 81 ms 59 ms 219.93.218.177
3 11 ms 10 ms 10 ms 219.93.216.77
4 10 ms 10 ms 10 ms 202.188.126.141
5 10 ms 10 ms 10 ms 202.188.126.132
6 10 ms 10 ms 11 ms 58.27.124.42
7 11 ms 10 ms 10 ms 219.93.173.133
8 210 ms 341 ms 210 ms 219.93.153.150
9 502 ms 503 ms 503 ms exchange-cust1.sv1.equinix.net [206.223.116.16]

10 506 ms 505 ms 503 ms ge-3-0-0-p261.msr1.scd.yahoo.com [216.115.106.18
7]
11 518 ms 506 ms 583 ms ten-1-3-bas2.scd.yahoo.com [66.218.82.219]
12 506 ms 504 ms 506 ms w2.rc.vip.scd.yahoo.com [66.94.234.13]

Trace complete.

C:\>ping www.google.com

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

Reply from 64.233.189.104: bytes=32 time=351ms TTL=247
Reply from 64.233.189.104: bytes=32 time=361ms TTL=247
Reply from 64.233.189.104: bytes=32 time=305ms TTL=247
Reply from 64.233.189.104: bytes=32 time=324ms TTL=247

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

C:\>ping www.hotmail.com

Pinging www.hotmail.aate.nsatc.net [211.206.123.219] with 32 bytes of data:

Reply from 211.206.123.219: bytes=32 time=443ms TTL=49
Reply from 211.206.123.219: bytes=32 time=436ms TTL=49
Reply from 211.206.123.219: bytes=32 time=451ms TTL=49
Reply from 211.206.123.219: bytes=32 time=480ms TTL=49

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



This post has been edited by rationale: Apr 24 2007, 09:40 PM

for me now 60.51 & 60.53 are the best can reach max speed midnight - morning

218.111.* is last month's story
60.49 used to be freaking fast beat 218.111.* last month

219.* 218.208.* 124.* never get

1000? that's good, I got 2400

Strange it is, why I never heard Jaring Broadband user complain? Jaring user didn't suffer high ping with Hinet Taiwan now?

This post has been edited by mashimarow: Apr 24 2007, 10:41 PM

its because slowmyx is much much better then them

Well that was on daytime, right now I got 2500

i cannot login to msn

I hate you but I love you, "dearest" TMNET.

I don't know why tech support seems to think that running their tmnet bandwidth test would help troubleshoot my current high latency to overseas IPs

this morning seems much better than las nite
p/s: where is the technician

Better? I got ping record of 3400ms+

where are they? kedai mamak minum tuak lah, where else

from 3000ms++ ping drop to 700ms, still slow like hell!!! what the hell is tmnet doing?

Constant maintenance exercises to experiment on the most effective way to save money, and squeeze every possible drop of b/w they have left.